Silence of Code Coverage – Time to Test the Tests
summary
This talk introduces mutation testing as a way to evaluate and improve unit tests when code coverage metrics look good but bugs remain. It explains how mutation testing mutates production code (creates small faults) to check whether unit tests detect them, helping reveal weak or missing test assertions and strengthen the test suite.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 1:15Tests and quality
- 2:39Code coverage problems
- 7:17What is mutation testing
- 9:50Mutation testing tools
- 12:47Mutation testing report example
- 15:21Limitations and false positives
- 17:09Mutation testing performance
- 19:18Speeding up mutation testing
- 21:44Implementation recommendations
- 23:08Mutation testing limits
- 24:12Testing as investment
- 25:39What and how to test
- 28:01Q&A
related talks
48mMutation Testing, or What Code Coverage Keeps Silent About
46mTest Your Tests Before They Betray You: Mutation Testing!
24mGain more confidence in your code with mutation testing
41mTest Your Tests by Introducing Bugs with Mutation Testing
38mMutants to the rescue: How effective are your unit tests?
30mMutation Testing, Finally a Good Measure of Test Quality?
43mMutation Testing, Finally a Good Measure of Test Quality?
41mMutation testing in practice
