Maven cross module tests #1361
Merged
Maven cross module tests #1361
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
hcoles
force-pushed
the
feature/cross_module
branch
from
82bdbd2
to
a94bd6a
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Initial support for cross module tests in maven.
When the parameter
<crossModule>is set for a maven module, pitest will now mutate both code defined within that module, and code defined within any module from the same project on which it depends.The checks for empty tests and code are disabled.
If care is not taken, setting the
crossModuleflag will result in results being reported for the same class in more than one module. If report aggregation is used, the behaviour is currently undefined.