4 ms·
The system under test could be considered as an input to the specification / test suite. Mutation testing could then be viewed as fuzzing of the test suite, wit
by feanaro 6y ago
The system under test could be considered as an input to the specification / test suite. Mutation testing could then be viewed as fuzzing of the test suite, with every pass result after a mutation being considered a failure of the test suite.
- pfdietz 6y agoAnd with the property-based approach, test inputs can be generated that automatically increase coverage or that kill mutants. The bane of mutation testing is equivalent mutants: mutations that aren't actually bugs, because they leave the program correct.
- nullc 6y ago> The bane of mutation testing is equivalent mutants: mutations that aren't actually bugs, because they leave the program correct. That's one reason I check the hash of the optimized binaries-- often the compiler manages to convert different but equivalent code into the same binary. It's still not enough, but it's an easy filter to apply with no false exclusions.
- pfdietz 6y agoGood idea.