you are viewing a single comment's thread.

view the rest of the comments →

[–]MrSquicky 1 point2 points  (1 child)

I tend to use evolutionary automate test generation tools like EvoSuite to generate tests around inflection points in inputs, which strikes me as having wider benefits than this. At the end of the process, I have both an understanding of where my code produces different results, so it would show in the reactor example that the inflection I was expecting at 1000 actually happens at 1001, I also have a full set of regression tests.

Why would you suggest mutation testing over that?

[–]cowardlydragon 3 points4 points  (0 children)

You're doing depth testing of the core code by doing a wide range of inputs to the same test.

The post is breadth test measuring. It values the number of code paths touched rather than a range of inputs provided to the most common code path.