Misleading message when project has no code to mutate about pitest

[Stephan202]

Hey @punkratz312! If I'm reading the screenshots right, you're using JUnit 5, but without the pitest-junit5-plugin. Can you try adding it?

[punkratz312]

Thank you @Stephan202

I have already tried that before without success:

pitest-junit5-plugin:

Project has no tests, it is empty:

test-classes:

pitest-parent:

pitest:

[hcoles]

The error message is misleading/wrong.

The problem is that the 'e2e-acceptance-tests' project has no production code to mutate, only test code.

[punkratz312]

Thank you for the hint @hcoles. That is kind of true, as the target code (to mutate) lives in another module and not directly in the executing 'e2e-acceptance-tests'-module. The code is still included and referred as a dependency.

Included and hopefully accessable for mutation:

Is therefore the byte code mutation not possible?

[hcoles]

Pitest doesn't support tests in a seperate module than the code under tests. From the name of the module, it sounds like these tests would not be suitable for mutation testing anyway. For practical reasons, mutation testing requires fast running unit tests. As a fundamental implementation detail, pitest requires tests that run in the same JVM as the code under test. This is often not the case for "end to end" tests that communicate with the code under test via http.

[punkratz312]

Thank you for the update; appreciate it. Perhaps a more precise error message would be helpful in making things clearer.

[punkratz312]

Seems to work fine with the end-to-end (E2E) stack. Yes, indeed, the tests actually only test the app black box over the web interface, just like the real client would do.

Still, achieving 100% line coverage with this method on a normal check:

This tremendous tool, Pitest, is capable of testing with this high-level approach as well as with normal unit tests, which is maybe what it was designed for in the first place.

Now it's actually the same code, all within one project. Thanks a lot!