What is "mutation testing," and what does it measure that traditional code coverage does not?
Correct! Well done.
Incorrect.
The correct answer is A) Mutation testing introduces small deliberate changes ("mutants") to the code and checks whether tests fail; it measures how effective a suite is at detecting faults, while code coverage only measures whether code ran, not whether tests catch bugs there
Correct Answer
Mutation testing introduces small deliberate changes ("mutants") to the code and checks whether tests fail; it measures how effective a suite is at detecting faults, while code coverage only measures whether code ran, not whether tests catch bugs there
A test suite with high code coverage might still fail to actually assert meaningful outcomes; mutation testing reveals this by checking if introduced faults ("mutants") cause test failures — if a mutant survives (tests still pass), it indicates a gap in test effectiveness.