Add ignoreExistingCoverage true #30
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
The project has a couple of tests that cover ~10% of the code. To generate 100% coverage for Java Demo on dashboard, we need this option. Previously, it was not needed to have this option explicitly set in this file because dashboard was setting it by default. This is no longer true due to platform API change.
|
It was tested on a VM (with last night's alfa build) that without the option, we only generate 90.7% coverage and with the option in diffblue.yml we get 100% coverage. |
allredj
approved these changes
Aug 19, 2019
JohnLBergqvist
approved these changes
Aug 20, 2019
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.
The project has a couple of tests that cover ~10% of the code. To generate 100% coverage for Java Demo on dashboard, we need this option. Previously, it was not needed to have this option explicitly set in this file because dashboard was setting it by default. This is no longer true due to a recent platform API change.