Fix missing expected lines in code coverage #269
Closed
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
fixes >100% coverage reporting - add all `getFuncCallText` to coverageMap recording - format `expectedCoverageMap` keys as key:value objects instead of arrays to match reporting Note: this doesn't add full branch tracking, but at least stops the incorrect percentage stats
|
Opened #271 with your changes and some extra sample code to validate it in the test app. |
|
Closing in favor of #271. Commits here are pulled into that PR. |
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.
fixes >100% coverage reporting
getFuncCallTextto coverageMap recordingexpectedCoverageMapkeys as key:value objects instead of arrays to match reporting formatNote: this doesn't add full branch tracking, but at least stops the incorrect percentage stats