mutation-testing
/mutation-testing
Measure how strong a test suite is by mutating the code and checking the tests notice, exposing assertions that never actually fail. Use when coverage is high but you doubt the tests would catch a real regression.
- Author
- Amey-Thakur ↗
- Repository
- AI-SKILLS ↗
- Licence
- MIT
- Last repository change
- 05.09.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 05.09.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Measure how strong a test suite is by mutating the code and checking the tests notice, exposing assertions that never actually fail. Use when coverage is high but you doubt the tests would catch a real regression.
Original author description
Measure how strong a test suite is by mutating the code and checking the tests notice, exposing assertions that never actually fail. Use when coverage is high but you doubt the tests would catch a real regression.
How it works
- Method
- Signals
- Boundaries
SKILL.md preview
--- name: mutation-testing description: Measure how strong a test suite is by mutating the code and checking the tests notice, exposing assertions that never actually fail. Use when coverage is high but you doubt the tests would catch a real regression. --- # Mutation testing Line coverage tells you a line ran, not that a test would fail if the line were wrong. Mutation testing closes that gap: a tool makes small changes to the code, flips a `<` to `<=`, replaces a return with a constant, deletes a call, then reruns the suite. A mutant the tests kill proves they guard that behavior. A mutant that survives is a hole coverage could not see, a line executed but never truly asserted. ## Method 1. **Run a mutation tool for your stack.** Stryker for JavaScript and C#, PIT for the JVM, mutmut or cosmic-ray for Python, cargo-mutants for Rust. Point it at the module whose tests you distrust, not the whole repo on the first pass. 2. **Read the mutation score as a diagnostic, not a target.** The score is killed mutants over total. Chasing 100% burns effort on equivalent mutants, changes that cannot alter behavior. Treat survivors as a reading list, not a number to maximize. 3. **Kill survivors by strengthening assertions.** A survivor usually means a test ran the line but asserted nothing about its effect. Add the assertion that pins the boundary the mutant moved, for instance `<=` versus `<` at a threshold. 4. **Recognize equivalent mutants and move on.** Some mutants leave behavior identical: reordering commutative operations, a timeout the tests cannot observe. Mark them ignored with a reason rather than contorting a test to kill something untestable. 5. **Scope runs to survive the cost.** Mutation testing reruns the suite once per mutant and is slow. Restrict it to changed files in CI with a `--since` diff mode, or run a full sweep on a schedule against critical modules. 6. **Gate only the code that matters.** For a payment or auth core, fail the build when new survivors appear. Elsewhere, run it periodically to find rotted tests instead of blocking every commit. ## Signals - Do surviving mutants cluster on branches the team assumed were tested? - After you kill a survivor, does the new assertion fail if you reintroduce the original bug by hand? - Is the runtime scoped so mutation testing informs work rather than blocking it? ## Boundaries Mutation testing grades an existing suite, it does not write tests or choose what to cover: pair it with unit-test-design to fill the holes it finds. Equivalent mutants and runtime cost make it a periodic audit for critical code, not a gate on every file.
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · Amey-Thakur/AI-SKILLS | 90 | MIT |
| proffesor-for-testing/agentic-qe | 100 | MIT |
| trailofbits/skills | 100 | CC-BY-SA-4.0 |
| laurigates/claude-plugins | 100 | MIT |
| DnsQueen/orcinus-skills | 100 | MIT |
| craftos-dev/craftbot | 100 | MIT |
| nikeyes/stepwise-dev | 100 | Apache-2.0 |
| sebastiendegodez/skraft-plugin | 100 | GPL-3.0 |
| thedaviddias/front-end-checklist | 100 | MIT |
Database snapshot: 13.11.2026 · package version 218dab444cc9 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100mutation-testing-python
Check whether Python tests actually catch bugs by mutating the code and seeing if the tests fail. Use after a Python slice passes its tests, before calling it done, and whenever a Python test suite looks green but unproven. Python only. Only invoke via the orcinus router. - 100running-mutation-tests
Execute mutation testing to evaluate test suite effectiveness. Use when performing specialized testing. Trigger with phrases like "run mutation tests", "test the tests", or "validate test effectiveness". - 100mutation-testing-specialist
Uses mutation testing results, or manual mutation reasoning, to find weak or missing assertions and propose tests that kill surviving mutants. Use when tests pass but you doubt they would catch real defects. - 100mutation-testing-specialist
Uses mutation testing results, or manual mutation reasoning, to find weak or missing assertions and propose tests that kill surviving mutants. Use when tests pass but you doubt they would catch real defects. - 100mutation-test
Run mutation testing to validate test quality beyond code coverage. Use when assessing test effectiveness, finding weak tests, or validating test suite quality. - 100mutation-test
Run mutation testing to validate test quality beyond code coverage. Use when assessing test effectiveness, finding weak tests, or validating test suite quality.