False error: Mutation testing requires a green suite

I am running pitest against a green suite. Though specific test classes fail when run with pitest.

The failing test classes have the following annotations:

@RunWith(SpringJUnit4ClassRunner.class)
@ContextConfiguration(locations = "/domain-test-context.xml")

This setup is being used so that we test code against a real DB.

If I am not mistaken these annotations is the reason these classes fail when being run by pitest.

Is this solveable ?

If not then is it possible to somehow configure pitest to ignore such tests ?

[galovics]

I haven’t used rules for this purpose but if this is the trend, it can be supported as well. I like to do small steps to the goal and this is the first one (excluding by runners). Let’s see how it works and how people use it, then we can continue developing this option.

I heard about JUnit categories as well but if you have hundreds or thousands of tests, you don’t want to categorize them one-by-one; but yeah, this might be an option for other projects.

[hcoles]

@StefanPenndorf I agree we should close this one. I think there may be a feature request in here to support filtering out tests that use certain junit rules, but I think that can be raised seperately if it is still something people would find useful in 2020.