Mutation Testing in JavaScript
summary
Mutation testing for JavaScript uses the Striker tool (npm install striker; striker run) to create mutants (binary, boolean, statement removal) and shows it finds weaknesses that coverage misses — a demo calculator with 100% line coverage still leaves ~50% of mutants alive. The talk explains TypeScript support, practical workflow, real limits on large codebases (~10k LOC) including performance and dynamic-import issues, and recommends running mutation tests periodically and tracking mutation score instead of running them on every commit.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 8:59What is mutation testing
- 12:36Striker setup first run
- 18:30Mutation types in Striker
- 24:44Mutation testing limits
- 35:49Q&A
- 46:53Summary
related talks
26mMutation Testing
07mWho is Testing the Tests?
21mKilling Mutants with Mutation Testing
41mMutation testing in practice
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?
