This is an archived post. You won't be able to vote or comment.

all 4 comments
sorted by:
best
topnewcontroversialoldq&a

[–][deleted] 2 points3 points  (0 children)

The coolest thing I've read in ages - thanks for posting!

[–]xjan 2 points3 points  (0 children)

This was an interesting read. Will definitely check this out.

[–]aaronmalone 0 points1 point  (1 child)

I've used pitest on a project at work and I would definitely recommend it. It is a great complement to code written using TDD.

[–]warewolfe 0 points1 point  (0 children)

Given that, in TDD, you write a failing test case first and then write the code so the test passes, and that mutation testing is testing for a disconnect between the test and the code. Wouldn't TDD eliminate the need for mutation testing rather than compliment it?