[capture] Naming convention for capture commands
Open
@vrozic is already working on this.
Since Aug 17, 2023.
Priority:P2
- Dominant language
- Jupyter Notebook
- Stars
- 43
- Forks
- 34
- PR merge metrics
- No merged PRs in 30d
Description
Test capture script #150 uncovered a problem with naming of some of the capture commands and arguments. At the moment we don't use consistent naming strategy, which makes it complicated to automate the testing. Since the repository is likely to be extended with newer tests, we should come up with a consistent naming strategy to make maintaining easier.
Tasks:
- [ ] Document the naming strategy
- [ ] Modify `capture.py` and the test scripts.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.