Home › Software Testing › Software Testing › advanced_security_performance › Mutation testing 'kills' a mutant when
Mutation testing 'kills' a mutant when
AAt least one test fails on the mutated code
BAll tests pass on the mutated code
CTests run faster on the mutated code
DMutated code compiles without errors
Answer & Solution
Correct answer: A. At least one test fails on the mutated code
A mutant is 'killed' when tests detect the mutation (some test fails). Surviving mutants suggest weak coverage. Mutation score = killed / total mutants (often equivalent mutants are excluded).
Related questions
Test coverage is BEST described asContinuous Testing in DevOps meansIn the V model of SDLC, system testing corresponds to'Test data' management addressesIn ISTQB terminology, a 'test oracle' isAcceptance Test Driven Development (ATDD) emphasisesTest Driven Development uses the rhythm ofRecovery testing simulates