Mutation Testing - CI/CD Glossary Definition
Mutation testing evaluates test quality by seeding bugs and measuring how many the tests catch.
Mutation testing deliberately introduces small faults (mutants) into the code, then checks whether the test suite fails. Surviving mutants reveal weak or missing assertions.
Unlike coverage, which only shows what ran, mutation testing shows whether the tests actually verify behavior. Tools include Stryker, PIT, and mutmut.
In CI
Mutation testing is expensive because it reruns tests per mutant, so teams often run it on changed files or on a schedule rather than every push.
Related guides
Mutation Score - CI/CD Glossary DefinitionMutation Score: Mutation score is the percentage of introduced mutants that the test suite detected (killed)…
Test Coverage - CI/CD Glossary DefinitionTest Coverage: Test coverage is the percentage of your code (lines, branches, or functions) that is executed…
Property-Based Testing - CI/CD Glossary DefinitionProperty-Based Testing: Property-based testing checks that a property holds for many automatically generated…