Mutation Testing
summary
Mutation testing measures test quality by generating code variations and checking whether the test suite kills them For a NodeJS project this uses Stryker.js and can create 20β30k mutants for 6β10k lines of code The example shows 100% line coverage but only a 65.8% mutation score with 27 mutants killed and 14 surviving Reports show red dots on lines to fix CI integration, parallel runs, and perβfile thresholds make it practical and actionable
AI-written summary Β· about
chapters (8)
- 0:00Mutation testing intro
- 1:05How mutation testing works
- 3:34Problems mutation testing solves
- 5:21Safe refactoring with mutation
- 7:49Best practices for mutation
- 10:17Thresholds and CI/CD
- 12:04Live mutation testing demo
- 18:29Real-world impact
related talks
07mWho is Testing the Tests?
41mMutation testing in practice
50mMutation Testing in JavaScript
36mMutation Testing: Did my test break my code ? π€
47mMutation Testing: Did my test break my code ? π€
22mKill All Mutants! (Introduction to Mutation Testing)
18mAttack of the mutants using mutation testing to improve your test suite
29mWho is testing the test?
