From jUnit to Mutation-Testing
summary
Claims that line coverage lies and mutation testing shows what tests actually exercise code paths, using JUnit as the test harness and Pitest (via Maven) to generate and run mutants, with JaCoCo still used for line coverage. An example run creates 54 mutants for a tiny method, reports which mutations are killed vs survived, and prompts writing targeted tests, removing redundant ones, or refactoring into smaller modules so mutation run time drops to 2–5 minutes and the overall test suite becomes both smaller and stronger.
AI-written summary · about
chapters (12)
- 0:00Introduction and context
- 3:00Testing challenges
- 5:27Line coverage limitations
- 9:53Mutation testing principles
- 13:57Types of mutations
- 19:22Tooling and process
- 22:40Project structure impact
- 25:51PITest framework
- 28:41Practical example
- 37:41Benefits of mutation testing
- 40:23Implementation steps
- 45:15Q&A and conclusion
related talks
38mMutants to the rescue: How effective are your unit tests?
43mMutation Testing
45mMutation Testing
41mMutation testing in practice
48mMutation Testing, or What Code Coverage Keeps Silent About
45mJulius Mischok: Test Your Tests!
20mMutation Testing: how to evaluate the effectiveness of your tests?
36mMutation Testing: Did my test break my code ? 🤔