-
Notifications
You must be signed in to change notification settings - Fork 353
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Not all relevent tests run for mutation in 1.1.1-2 #158
Comments
Thanks for reporting this. I've just managed to reproduce it locally. I don't yet understand the issue, but it most likely relates to the block based coverage system that was introduced 1.1.1. |
Commenting out testValidateOk causes the mutation to be killed. Hmm. |
Ok found the issue. When a line is contained within more than 1 block and is covered by multiple tests, if some of those tests hit only 1 of those blocks the full set of covering tests is not seen as only the tests for one of those blocks is used. I'd rank that as very serious - I'll get a fix out ASAP. Thanks again for reporting it. |
Ok, thanks. |
Should be syncing across to maven central now after a battle with the gpg plugin. |
Hello,
I think I've found a bug in pitest 1.1.1 and 1.1.2 with Void Method Call Mutator.
I have a simple class:
and a test:
All possible cases and mutations are covered. However pitest says:
for line:
which is not true, because if I remove this line the first test testValidateEmpty does not throw IllegalStateException and, of course, fails.
If I change the version of pitest to 1.1.0 it works fine, so it must have been broken somewhere in 1.1.1.
The text was updated successfully, but these errors were encountered: