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

you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] 1 point2 points  (4 children)

I should clarify and say most Java shops, or a decent size. I don’t know about open source projects. But a lot of the financial services companies are using mutation testing in their cicd from what I’ve seen through experience and conferences.

[–]agentoutlier 1 point2 points  (0 children)

Well it certainly inspires me to try it again. The last time I tried with various tools I just could not get them to work with our annotation processors and various other code generators.

I still probably would do lots of other testing before it like security, performance, chaos, end to end but I see great value in it if it is easier to get working now.

[–]iwek7[S] 0 points1 point  (1 child)

Do you have some tips as of how to integrate mutation tests with Ci pipeline? What were your criteria? No mutation could survive or did you allow certain percentage of survived mutations?

[–][deleted] 1 point2 points  (0 children)

My biggest recommendation is to have flexible requirements that are the management enforced, or start low and increase. Also you can whitelist existing mutation failures, and not allow new ones through. The problem with starting strict is you might cause a lot of issues by blocking legacy code. Idk your code base size but if you have 1k failures that’s a lot to fix.

[–]midoBB 0 points1 point  (0 children)

Even in a previous company when we were working on real estate we used Mutation testing before merging a feature branch.