Who is testing the test?
summary
Shows mutation testing proves test effectiveness beyond code coverage by mutating a demo bar app and running StrykerJS against its unit suite. It generates 126 mutants, runs the existing 16 tests, surfaces surviving mutations (example: age check and count logic), then tests are tightened and the project score climbs from 58% → 85%. Configuration notes, concurrency and coverage-guided test selection are demonstrated, and the approach visibly finds real gaps and fixes them.
AI-written summary · about
chapters (15)
- 0:00Mutation testing introduction
- 1:56Demo app overview and age check
- 6:48Code coverage limits
- 7:08How mutation testing works
- 10:58Mutation testing frameworks
- 12:22Striker.js for JavaScript
- 13:25Configuring Striker.js
- 17:40Running Striker.js and results
- 19:15Analyzing mutation reports
- 21:00Fixing failing tests
- 23:49Debugging test failures
- 25:13Rerunning after fixes
- 26:37Improved score and next steps
- 28:03Why mutation testing matters
- 29:05Closing and resources
related talks
07mWho is Testing the Tests?
18mAttack of the mutants using mutation testing to improve your test suite
21mKilling Mutants with Mutation Testing
41mMutation testing in practice
24mWho is testing your tests?
26mMutation Testing
50mMutation Testing in JavaScript
47mMutation Testing: Did my test break my code ? 🤔