Test Quality Review
Use current primary guidance as a review baseline, then report only what the available evidence supports. Primary authority: official reference.
Workflow
- Identify the behaviors and risks the tests are expected to protect.
- Trace representative tests from setup through action, oracle, cleanup, and failure output.
- Check that assertions can fail for the target defect and are not coupled only to implementation details.
- Review boundary, negative, concurrency, retry, migration, permission, and recovery coverage where relevant.
- Inspect isolation, determinism, clocks, randomness, network, shared state, fixtures, and parallel safety.
- Find skipped, quarantined, flaky, snapshot-heavy, redundant, slow, or low-signal coverage.
- Recommend focused mutations or controlled defect injection to test sensitivity when authorized.
Boundaries
- Do not equate test count, line coverage, or a green suite with meaningful behavioral protection.
- Do not weaken assertions or accept broad snapshots merely to reduce failures.
- Do not execute destructive fixtures or shared-environment tests without explicit authorization.
Output
Return Protected behavior, Oracle quality, Missing risks, Flakiness and isolation, Maintenance cost, and Recommended evidence.
1---2name: test-quality-review3description: Review the quality of a test suite or change-specific tests for meaningful assertions, defect sensitivity, isolation, determinism, risk coverage, and maintenance cost. Use when existing gates pass but the strength of the tests themselves is uncertain.4license: MIT5---67# Test Quality Review89Use current primary guidance as a review baseline, then report only what the available evidence supports. Primary authority: [official reference](https://docs.python.org/3/library/unittest.html).1011## Workflow12131. Identify the behaviors and risks the tests are expected to protect.142. Trace representative tests from setup through action, oracle, cleanup, and failure output.153. Check that assertions can fail for the target defect and are not coupled only to implementation details.164. Review boundary, negative, concurrency, retry, migration, permission, and recovery coverage where relevant.175. Inspect isolation, determinism, clocks, randomness, network, shared state, fixtures, and parallel safety.186. Find skipped, quarantined, flaky, snapshot-heavy, redundant, slow, or low-signal coverage.197. Recommend focused mutations or controlled defect injection to test sensitivity when authorized.2021## Boundaries2223- Do not equate test count, line coverage, or a green suite with meaningful behavioral protection.24- Do not weaken assertions or accept broad snapshots merely to reduce failures.25- Do not execute destructive fixtures or shared-environment tests without explicit authorization.2627## Output2829Return Protected behavior, Oracle quality, Missing risks, Flakiness and isolation, Maintenance cost, and Recommended evidence.30
JovaniPink