Test Coverage

Write valuable tests that improve confidence and coverage. Prefer behavior that is likely to regress, not low-signal assertions written only to inflate percentages.

Quick Start

1. Explore the repository structure and identify source, test, and coverage config files.
2. Run scripts/repo_test_probe.py from the skill directory against the target repo to infer the stack, test tooling, and coverage artifacts.
3. If coverage reports already exist, use them to find cold spots. Otherwise infer gaps from changed code, complex logic, public APIs, and error-handling branches.
4. Write tests in the project's existing style and framework.
5. Run the narrowest relevant test command first, then broader coverage runs if needed.
6. Iterate until the new tests are stable, meaningful, and improve practical coverage.

Workflow

1. Detect how the project tests itself