Generate coverage for Simulator based integration tests & ui tests in github actions#7784
Conversation
Codecov Report
@@ Coverage Diff @@
## main #7784 +/- ##
=============================================
+ Coverage 13.42% 29.27% +15.85%
- Complexity 9383 30265 +20882
=============================================
Files 2747 5098 +2351
Lines 258827 357598 +98771
Branches 40318 52212 +11894
=============================================
+ Hits 34748 104703 +69955
- Misses 219694 238360 +18666
- Partials 4385 14535 +10150
Flags with carried forward coverage won't be shown. Click here to find out more. see 3628 files with indirect coverage changes 📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
|
I found these tests that are not included in the |
I would not include any effort on those in this PR @vishesh92 . Best would be to create a tracking issue to decide which ones to delete/fix/add. |
|
@blueorangutan package |
|
@DaanHoogland a [SF] Jenkins job has been kicked to build packages. It will be bundled with KVM, XenServer and VMware SystemVM templates. I'll keep you posted as I make progress. |
|
Packaging result [SF]: ✔️ el7 ✔️ el8 ✔️ el9 ✔️ debian ✔️ suse15. SL-JID 6626 |
|
@vishesh92 good work and proposed PR, we may need a different way to track this perhaps? All tests in smoke should be ideally run against simulator/ci.yml, but other tests arne't included as they fail or amount of effort to stablise them would be huge. smoke/test_gateway_on_shared_networks |
| - name: Start CloudStack Management Server with Simulator | ||
| run: | | ||
| export MAVEN_OPTS="-Xmx4096m -XX:MaxPermSize=800m -Djava.security.egd=file:/dev/urandom" | ||
| export MAVEN_OPTS="-Xmx4096m -XX:MaxPermSize=800m -Djava.security.egd=file:/dev/urandom -javaagent:jacoco/lib/jacocoagent.jar=address=*,port=36320,output=tcpserver" |
There was a problem hiding this comment.
perhaps we can experiment this with our smoketests against actual environment and gather/publish the jacoco file separately cc @vishesh92 @borisstoyanov @vladimirpetrov @kiranchavala @DaanHoogland - so we've a unit test coverage stats and functional/marvin test coverage stats (discuss - if you think, combined is also okay?)
There was a problem hiding this comment.
@rohityadavcloud We can get the coverage from Blue Orangutan jobs. I can do that as well, but I don't have much idea about the setup as of now. So, I will need some time to look into it.
There was a problem hiding this comment.
I would certainly like to have them separately, but nobody dies if we don't.
|
@vishesh92 Does this handle reports from multiple jobs and aggregate them somewhoe; could you look into (when you're free/have time): https://about.codecov.io/blog/uploading-code-coverage-in-a-separate-job-on-github-actions/ |
|
@rohityadavcloud As per my understanding, codecov groups the coverage by flags. See uploaded files for this PR here: https://app.codecov.io/gh/apache/cloudstack/commit/c944865bd84a1fab86755bc164123c64291adce1 |
|
@blueorangutan package |
|
@DaanHoogland a [SF] Jenkins job has been kicked to build packages. It will be bundled with KVM, XenServer and VMware SystemVM templates. I'll keep you posted as I make progress. |
|
Packaging result [SF]: ✔️ el7 ✔️ el8 ✔️ el9 ✔️ debian ✔️ suse15. SL-JID 6797 |
yadvr
left a comment
There was a problem hiding this comment.
LGTM - changes are in the github actions
Description
This PR generates coverage for Simulator based integration tests in github actions workflow and uploads the report to codecov.
Types of changes
Feature/Enhancement Scale or Bug Severity
Feature/Enhancement Scale
Bug Severity
Screenshots (if appropriate):
How Has This Been Tested?