Enabled combination of forceCoversAnnotation and processUncoveredFilesFromWhitelist #42
Conversation
This file contains hidden or 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
sebastianbergmann
added a commit
that referenced
this pull request
May 6, 2011
Enabled combination of forceCoversAnnotation and processUncoveredFilesFromWhitelist.
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.
When forceCoversAnnotation is activated, files are completely ignored in coverage reports, if they do not have any coverage at all. This means, they are missing from the report at all.
This shouldn't happend, if processUncoveredFilesFromWhitelist is activated at the same time.
Therefor I provided a little patch which puts all files into the coverage report, even if they did not have any covered code lines and processUncoveredFilesFromWhitelist is activated at the same time.