Untested business logic
Suitable when the scope and expected result can be made explicit before implementation.
Test Coverage Sprint
Protect the behavior that matters before it becomes the next regression.
We inspect the relevant code and existing test path, agree on the behaviors worth protecting, add focused coverage, run the evidence, and independently review the test changes.
Good fit
Bounded work with a visible finish line.
Regression coverage for a recent bug
Suitable when the scope and expected result can be made explicit before implementation.
Edge-case and error-path coverage
Suitable when the scope and expected result can be made explicit before implementation.
Flaky or brittle test cleanup
Suitable when the scope and expected result can be made explicit before implementation.
Read-only preflight
What we verify first.
Preflight gathers evidence. It does not authorize implementation.
Existing test framework and commands
Captured as evidence for qualification and the Sprint Brief before implementation begins.
Target modules / behaviors
Captured as evidence for qualification and the Sprint Brief before implementation begins.
Current baseline failures
Captured as evidence for qualification and the Sprint Brief before implementation begins.
Important edge cases and do-not-touch behavior
Captured as evidence for qualification and the Sprint Brief before implementation begins.
Lane use
Implementation stays inside the approved brief.
The implementation lane adds tests and the minimum supporting changes required by the brief. A separate review checks that tests exercise real behavior instead of merely inflating coverage numbers.
Definition of done
Evidence before handoff.
Targeted tests pass, the agreed behaviors are covered, full-suite results are recorded, and product behavior is unchanged unless the brief explicitly says otherwise.
Client controls merge. Deploy remains off by default.