Drive coverage to 100%
Find uncovered behavior, add tests that actually matter, and stop when the full suite passes at 100%.
Use this when
Use this when 100% coverage is an explicit project requirement and the repository has a trustworthy coverage command, clear exclusions, and a test suite that can be run repeatedly.
How it runs
- Run the complete test suite with coverage and save the baseline report.
- Prioritize uncovered branches and behavior by risk instead of file order.
- Add tests that assert meaningful outcomes, failure paths, and boundary conditions.
- Repeat until the full suite passes and the configured coverage report reaches 100%.
Done when
✓ The full test suite passes at 100% coverage. Use the project's coverage report as the source of truth.
Why it works
A concrete coverage target gives the agent a measurable stopping condition and makes skipped code visible. Risk-first ordering keeps the work focused on behavior that matters.
Implementation note
Coverage measures which code ran, not whether the assertions are good. Review test quality, avoid tests that only execute lines, and keep justified generated-code or platform exclusions explicit.
More testing loops
Watch tests while you work
A passive watchdog loop that reruns your test suite every 15 minutes and surfaces failing tests with their error output.
Kill flaky tests
Run your test suite repeatedly, collect every intermittent failure, and fix or quarantine flaky tests until you get five consecutive green runs.
Make all tests pass
Implement remaining code and run tests repeatedly until the full suite passes.