-
Notifications
You must be signed in to change notification settings - Fork 206
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Code coverage report is calculated before running tests #2227
Conversation
I don't see any code coverage results for this build. How was the number 28 computed? |
Codecov Report
@@ Coverage Diff @@
## main #2227 +/- ##
==========================================
- Coverage 83.67% 83.61% -0.06%
==========================================
Files 151 151
Lines 28214 28249 +35
==========================================
+ Hits 23608 23621 +13
- Misses 4606 4628 +22 see 53 files with indirect coverage changes Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I believe there are more than 6 cases.
Signed-off-by: Dave Thaler <dthaler@microsoft.com>
closes #1884
Description
code cov calculates the coverage of tests right before CI/CD build and even running any tests( #1866 (comment)).
This will create confusion whether the coverage change is correct or not. In fact, it computes the numbers before all the tests are complete, which is skewing the numbers.
Testing
Updated the number of
after_n_builds
to reflect the correct threshold. More information about this flag is listed here.Documentation
N/A