MutationTesting
Deliberately breaking code to check whether the test suite actually catches it — a test-suite-quality check, not a correctness check.
Why we need this / what value this brings
Reveals whether your test suite actually catches bugs, or just executes code without asserting anything meaningful.
When to use this
Once there's a substantial test suite worth auditing for quality — not useful on a thin or early-stage suite.
How to use or implement this
Run it periodically as a suite-quality check, not as a blocking CI gate — it's slow and its findings need human judgment.
Research questions
- Purely a maturity-signal tool — worth revisiting once the test suite itself is substantial enough to audit.
Empty folder — drop notes, links, and findings here as you research.