← Graph

Should every project use mutation testing?

question 2 connections

Audience member asks whether mutation testing is appropriate for every project/client, and whether to focus on core domain/business logic first. Schirp's answer: yes to every project — human time is the most expensive resource and Mutant takes ~10–20 seconds per subject. And no to restricting to core domain — any line of code can blow up in production (even a rendering glitch shows on every page), so trying to find the 'perfect place' to mutation-test is fruitless, especially in Ruby where everything can kill everything. Recommends running it everywhere because it is cheap compared to human time.

answer_summary
Use mutation testing on every project and everywhere in the codebase — not just core domain — because it is far cheaper than human review time.
question Should every project use mutation testing?
about
Question is about scope of adoption.
question Should every project use mutation testing?
asked_at
Audience question during the Q&A.

Provenance

Read by
1 extraction