Test coverage
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 344
- Forks
- 74
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 7
Description
Test coverage is somewhat spotty right now. Plenty of the core pieces are covered, along with actual bugs that were discovered by usage, but there are plenty of obvious gaps in our current verification.
Any contribution to increase coverage of the pytest tests is welcome.
Note that these tests do not have a usable py command, and so need to be structured to not rely on that - plenty of mocks, monkey-patching and directly importing commands is intended!
(For tests that can only be run after the full app is compiled/installed, create a new issue describing the scenario and why you think it wouldn't be valid as a unit test.)
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
Start by inspecting the existing pytest test suite and identifying an uncovered, unit-testable core area; the issue does not name specific files or entry points. Structure tests without relying on a usable py command, using mocks, monkey-patching, or direct command imports as needed. Done means adding focused coverage for a selected gap and keeping the tests valid without compiling or installing the full app.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100