Fix test coverage for JUnit4 tests #93
Merged
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
Signed-off-by: André Silva <[email protected]>
Signed-off-by: André Silva <[email protected]>
|
@martinezmatias this should be merged before #91 |
|
Thanks @andre15silva ! |
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.
This PR fixes the option
coverTestsbut only for JUnit4 tests. For some, still unknown, reason, for JUnit5 and JUnit3 the coverage is not working. (#41 )More importantly, this makes it so that test classes are excluded from the computation when the option is not set, even if they are included in the jacoco results.
The implementation is an alternative to specifying them in the
excludesoption of jacoco, since that option quickly runs out of stack space (see #57 )