-
Notifications
You must be signed in to change notification settings - Fork 49
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
Take inline overrides into account in mandatory_include and bootstrap_include sections of a test plan (BugFix) #1079
Conversation
…test plan Although inline overrides were taking into account in the `include` section of a test plan, it was not the case for the `mandatory_include` section. So a test plan like this: unit: test plan id: test-plan name: My test plan mandatory_include: mandatory-cert-blocker-job certification_status=blocker include: regular-cert-blocker-job certification_status=blocker would only make "regular-cert-blocker-job" a cert-blocker, not "mandatory-cert-blocker-job".
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #1079 +/- ##
==========================================
+ Coverage 40.92% 40.99% +0.07%
==========================================
Files 337 337
Lines 37548 37552 +4
Branches 6384 6385 +1
==========================================
+ Hits 15366 15396 +30
+ Misses 21543 21517 -26
Partials 639 639
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
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.
Small comment below
- Move the V class one level above, so it can be used for the different include sections of the test plan. - Fix issue found by Max (`mandatory_include` was parsed only if there was an `include` section) - Add support for `bootstrap_include` for good measure
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.
+1, ty
…_include sections of a test plan (BugFix) (canonical#1079) * Take inline overrides into account in mandatory_include section of a test plan Although inline overrides were taking into account in the `include` section of a test plan, it was not the case for the `mandatory_include` section. So a test plan like this: unit: test plan id: test-plan name: My test plan mandatory_include: mandatory-cert-blocker-job certification_status=blocker include: regular-cert-blocker-job certification_status=blocker would only make "regular-cert-blocker-job" a cert-blocker, not "mandatory-cert-blocker-job". * Add support for bootstrap_include section - Move the V class one level above, so it can be used for the different include sections of the test plan. - Fix issue found by Max (`mandatory_include` was parsed only if there was an `include` section) - Add support for `bootstrap_include` for good measure * Add unit test to check bootstrap_include inline overrides
Description
Although inline overrides were taking into account in the
include
section of a test plan, it was not the case for themandatory_include
andbootstrap_include
sections.So a test plan like this:
would only make "regular-cert-blocker-job" a cert-blocker, not "mandatory-cert-blocker-job".
Resolved issues
Tests
Tested by running a test plan similar as the one described above and making sure the HTML report includes the job in
mandatory_include
andbootstrap_include
sections as a cert-blocker.