Add unit tests
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1k
- Forks
- 203
- Avg merge
- 1h 20m
- Merged PRs (30d)
- 2
Description
There are a number of full-stack tests, but few unit tests.
A few cleanup items that would help:
- #160
- #164
- raise a new
CommandFailedErrorin internal code instead of callingsys.exit()
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
Review the related cleanup issues #160 and #164, then inspect the internal code paths that currently call sys.exit(). Determine which behaviors need unit coverage and where CommandFailedError should replace those exits. Done means the relevant unit tests exist and the internal failure behavior is covered without relying on full-stack tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- testing-qa
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100