Testing with Mutants
summary
Prototype mutation testing for Clojure generates mutants via rewrite-clj transforms, recompiles affected namespaces with a dependency graph, and runs tests through a lein mutate plugin that reports survivors. Key claims: mutation finds real omissions that coverage misses; sampling pays off — 10% → 80% of survivors; running per-commit in CI and targeting only changed lines makes it tractable. Known limits: it is slow, can produce nonterminating mutants, and JVM process isolation is awkward, so parallelization and test selection are essential.
AI-written summary · about
chapters (6)
- 0:00Start
- 2:41Who is testing our tests?
- 3:08Competent programmer
- 4:45Coupling effect
- 17:56Mutate continuously
- 19:56Introduce it gradually
related talks
42mTesting with mutants
50mKill All Mutants! Intro to Mutation Testing
01h 00mKill Evil Mutants!
41mMutation Testing with Mutant
47mKill All Mutants! (Intro to Mutation Testing)
22mKill All Mutants! (Introduction to Mutation Testing)
38mMutants to the rescue: How effective are your unit tests?
41mMutation testing in practice