Mutation testing in practice
summary
Shows that injecting small, automated code changes reveals real blind spots: projects report 100% line coverage but surviving mutants, proving tests miss logic and assertions. Uses Java PIT and JavaScript Stryker, runs mutations in parallel to speed reports, emits HTML diffs that highlight which mutators survived. Example metrics: a live poll shows ~96% of attendees have unit tests yet most say they do not fully trust tests. Advises running mutation testing locally, not as a mandatory slow CI gate.
AI-written summary · about
chapters (11)
- 0:00Welcome and introduction
- 2:10What is quality in testing
- 6:45Testing pyramid overview
- 11:03Limitations of code coverage
- 17:46Mutation testing concept
- 23:42Why mutation testing matters
- 24:46Mutation testing tools overview
- 31:11Full-stack mutation testing
- 33:24Mutation testing in practice
- 35:52Key takeaways and summary
- 36:15Q&A session
