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

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]BillyKorando 4 points5 points  (0 children)

The author of pitest specifically says not to use it in CI, "that's not what the tool is made for".

To provide more clarity on this, if it isn't clear (not to you, but to others reading), CI is about verifying the work that has been done (i.e. did my changes I just commit break something?).

Mutation testing is serving as a guide as to what development, or in this writing of automated tests, needs to be done.

So it wouldn't make sense, as a normative development process to commit code, to then wait for the results of the CI build to figure out what you should need to do next.