test-audit
Test Audit
Optimize for confidence, not for deletion count. A test earns its place when it
protects a behaviour, a credible regression, or a contract that matters on its
own. The rules are the project's test rules in its coding standard, including
the junk patterns. If the project has none, use the baseline in
coding-standard's references/baseline-rules.md, and tell the user to adopt
it.
For one whole subsystem in one PR, follow references/campaign.md instead of step 3 to step 5.
1. Scope
Agree the scope with the user: one module, one folder, or one pattern across
the repo. Pin the base commit: git rev-parse HEAD. Run the scope's tests once
on it and record each file's result. A test that fails on the base is a
possible product bug. Reproduce it and report it; never delete it.