tests-purge-unneeded

To identify tests not catching real bugs, articulate the specific failure mode each test guards against. If a test cannot surface a meaningful defect, it is dead-weight noise and should be removed to keep your suite lean.

Delete tests during CI sweeps or refactors when the test no longer guards real boundaries like I/O, error handling, or security. Ensure deletions are atomic commits with explicit rationale to suppress noise while preserving critical coverage.

The best way to remove unneeded tests without losing coverage is to verify the remaining suite still exercises core paths at boundary contracts. Purge tests individually with a one-line rationale for each atomic commit.

Mutation testing helps justify test deletion by revealing if a test actually surfaces defects. If a test fails to detect mutated code, it lacks real-bug value and can be safely purged to reduce maintenance cost.

Deleting low-value tests improves quality assurance by reducing maintenance cost and CI time. Volume is not a quality signal; removing tests that fail to catch real bugs ensures the suite pays rent by only guarding critical boundaries.

Yes, you can use this workflow to guide PR reviews for test reductions. It requires developers to articulate the real-bug failure mode for each candidate test and justify the removal with an explicit one-sentence rationale.