-
Notifications
You must be signed in to change notification settings - Fork 30
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
Include integration tests in code coverage calculation #427
Conversation
Signed-off-by: Daniel Grimm <dgrimm@redhat.com>
Hmm this takes way too long and is going to eat up our GH actions budget. Will check if we can just upload after running the tests in prow. /hold |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #427 +/- ##
===========================================
+ Coverage 60.19% 77.22% +17.03%
===========================================
Files 34 34
Lines 1638 1638
===========================================
+ Hits 986 1265 +279
+ Misses 600 301 -299
- Partials 52 72 +20 ☔ View full report in Codecov by Sentry. |
Removing the hold. Apparently, as our org is a CNCF org, they should be paying for GitHub Actions. Let's find out :) |
So this re-runs all the tests even though we already run them in the other jobs? Isn't there an option to generate a coverage file there and then use that file to generate this report? |
I'm looking at removing the prow jobs if we have enough GitHub action budget, and then only running the github actions for unit and integration tests. The problem with generating the profiles in the prow jobs is the following:
|
Why not? |
people running it won't let us |
* upstream/main: Include integration tests in code coverage calculation (istio-ecosystem#427) Improve failure messages for supportedversion unit tests (istio-ecosystem#442)
* upstream/main: Add spec.values.global.platform to IstioCNI (istio-ecosystem#443) Include integration tests in code coverage calculation (istio-ecosystem#427) Improve failure messages for supportedversion unit tests (istio-ecosystem#442)
This makes sure we're also measuring code coverage for our integration tests. I hope codecov is smart enough to merge the files.