Attack of the mutants using mutation testing to improve your test suite
summary
Shows mutation testing with StrykerJS against standard coverage from Istanbul, claiming mutation score measures test effectiveness not just execution. Gives a concrete audit of nv d3 scatter chart: 84% coverage vs 21% kill after ~500 mutants, finds an 800-line “mega” function and slow tests that make mutation runs impractical. Recommends narrowing mutation to changed files, speed up tests and fix memory leaks, run on multiple CPU cores, and use the HTML mutant report to see which specific mutants survive.
AI-written summary · about
chapters (9)
- 0:00The limitations of coverage
- 2:05Analyzing project testing
- 4:49Introduction to mutation
- 7:26Mutation testing in action
- 9:21Balancing testing strategies
- 11:04When to apply mutation tests
- 12:25Configuring Stryker
- 14:05Best practices and caveats
- 17:12Conclusion
