fix: remove filter on coverage measurement #320
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
BainanXia
approved these changes
Sep 3, 2021
We thought it was skewing the results to have 100% coverage on many test files. But realized that is fine/expected, better to measure coverage on everything and just have a different baseline. |
Aha, make sense. a/b < a+c/b+c when 0 < a < b and c > 0. |
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.
Purpose
We forgot to update the config here, so coverage is appearing lower than it should (at least relative to the other repos).
What the code is doing
Stop excluding test files in the measurement.
Testing
n/a
Time estimate
1 min