jackfirth / jackfirth/resyntax
Maximize overall project test coverage
Open
Nobody has claimed this yet.
testing
- Dominant language
- Racket
- Stars
- 70
- Forks
- 11
- PR merge metrics
- No merged PRs in 30d
Description
Now that I've set up Coveralls, it's easier to tell where the test coverage gaps are. Resyntax currently has about 94% coverage but there's several specific files that have much worse than that. Let's see how close to 100% we can get.
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.
Research direction
Start with the Coveralls report for Resyntax and identify the specific files with coverage well below the project's roughly 94% overall level. Read those files and their existing tests, then add focused tests for the uncovered behavior. Done means the coverage gaps are substantially reduced and the test suite passes.
Written by the indexing model from the issue text.
Assessment
- Domain
- testing-qa
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 42/100