PIT cannot detect tests and classes when package starts with "com" about pitest

[hcoles]

If you share a minimum project that reproduces the issues I can take a look and see what is going on.

[hcoles]

Fixed in 1.15.7.

Thanks again for reporting.

[hcoles]

If you are using gradle, you must explicitly set the target classes parameter (this is automatically populated for maven). Pitest will only mutate classes that match this glob.

[kulasangeles]

Hi @hcoles thanks for responding promptly. I am using target class and what's weird is that there are certain combinations that seems to not detect classes and tests. I did a few tests. for com.sun.* - it does not detect the tests and classes but for ca.sun.* it was detected. Not sure what's wrong with the com.sun package name that makes PITest not detect the tests and classes.
Here are a few screenshots.

[hcoles]

'com.sun' is a package used in legacy parts of the JDK (from Java's roots at sun microsystems). Pitest will not mutate it as it could cause all sorts of problems.

[kulasangeles]

I see. Thank you. One last question before I close the issue. What if there are packages that starts with com.sundance for example - do we have a way to still run pitest on them?

[hcoles]

If your target is set to com.sundance.* that should work without issue.

[kulasangeles]

If your target is set to com.sundance.* that should work without issue.

It does not as per my tests

[kulasangeles]

test-learner.zip
Here's a very small gradle project I am working on. Thank you!

[hcoles]

Thanks for the project, this is indeed a (very old) and stupid bug in pitest.

The bit of the code that stops pitest from instrumenting jdk classes is missing a '.', so it is filtering "com.sun*" rather than "com.sun.*".

Should be fixed shortly.

[kulasangeles]

Thank you for fixing @hcoles!