The Mutation Game: Cracking the Enigma of Mutation Testing
summary
Shows mutation testing applied to a real Ruby app using the mutant gem and the parser gem, running about 20 mutations with 18 killed and 2 surviving before test and code changes push coverage to 100% on a method. Demonstrates concrete fixes: replace [] with fetch, add failing cases, remove stray puts, and change tests to catch edge cases. Notes runtime slowdown, occasional threading/parsing errors, inability to mutate eval/closure-defined methods, and a $90 per seat cost.
AI-written summary · about
chapters (11)
- 0:00Mutation testing intro
- 1:45What mutation testing does
- 4:39Benefits of mutation testing
- 6:24Ruby mutation tools
- 8:31Demo: Benedict vs X-Men
- 11:43Mutating array length
- 13:55Fixing average box office
- 16:25Box office data with median
- 18:54Validating UPC codes
- 21:00Limitations of mutation testing
- 23:29Adopt mutation testing?
related talks
27mThe Mutation Game: Cracking the Enigma of Mutation Testing
37mHow to Write Better Code Using Mutation Testing
41mMutation Testing with Mutant
36mMutation Testing: Did my test break my code ? 🤔
41mMutation testing in practice
01h 06mKill All Mutants! (Intro to Mutation Testing)
50mKill All Mutants! Intro to Mutation Testing
20mUnleashing the Power of Mutation Testing: Supercharging Software Quality and Resilien...