mutation-test-runner

Mutation testing exposes test gaps by generating code mutants from a catalog and evaluating whether your existing tests detect them. It computes a mutation score to measure test suite detectability and identify weaknesses, ensuring you catch real regressions before release.

To enforce zero surviving mutants in PR gates, apply mutation testing to evaluate generated code mutants against your test suite. The runner outputs a PASS, NEEDS REVISION, or BLOCKED verdict based on your domain-specific score thresholds and P0 zero-survivor gate requirements.

Yes, measuring mutation scores requires a domain config, source and test files, and a configured mutation runner. You must also provide domain-specific score thresholds to evaluate mutant detectability and produce a final release decision verdict.

Yes, mutation testing identifies weak assertions by generating code mutants that your tests should catch. If mutants survive, the runner provides weak-assertions guidance and reports to help you improve test coverage and strengthen your suite's bug detection capabilities.

The best way to use mutation testing for pre-release runs is to execute the runner against your repository to begin the first mutation wave. It enforces domain-specific mutation thresholds and P0 zero-survivor gates to ensure proper release engineering quality assurance decisions.

You should not rely solely on test coverage for bug detection when high-stakes release engineering is involved. Coverage does not measure assertion quality, whereas mutation testing verifies that your tests actually fail when code mutants are introduced, providing deeper quality assurance.