-
Notifications
You must be signed in to change notification settings - Fork 247
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
📖 Add trigger phrases and status badge for e2e tests #1525
📖 Add trigger phrases and status badge for e2e tests #1525
Conversation
3616c12
to
2c3daea
Compare
/test metal3-bmo-e2e-test-pull |
nice, LGTM |
Wait there is something wrong with the build badge. It doesn't show the correct text |
2c3daea
to
f4eee2c
Compare
Ok now it looks better |
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.
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: kashifest The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/test metal3-bmo-e2e-test-pull |
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.
LGTM
README.md
Outdated
@@ -39,6 +40,11 @@ Eventually these tests will be replaced with BMO's own | |||
[e2e tests](test/e2e/README.md). BMO e2e tests are currently under active | |||
development. Here are the tests which run on different branches in BMO: | |||
|
|||
**E2e tests:** | |||
|
|||
* **/test metal3-bmo-e2e-test-pull** runs required BMO e2e tests on your PR. Works for main and release-0.5 branches. |
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.
would be interesting to have a description of the tests included here and the optional ones too
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.
Good point! I wonder if it perhaps is a bit premature, at least for the optional tests? I'm afraid the list would be constantly changing (or worse, outdated).
Another question is if it should be here or in the test/e2e/README.md
?
What do you think?
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.
good point for the optional tests, let's wait a bit for when they're more "stable"
I guess adding the description for the required ones to test/e2e/README.md
and add a link here would work
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.
Updated, please take a look 🙂
f4eee2c
to
bfb98e4
Compare
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.
One nit.
bfb98e4
to
66fae19
Compare
LGTM, I'll leave it to @elfosardo to flag it if he's also happy. |
66fae19
to
a5af56a
Compare
a5af56a
to
2ade793
Compare
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.
/lgtm
This adds the trigger phrases for the e2e tests to the README.md and also the build badge for the periodic job. The two e2e test sets are described a bit more in the e2e README.md. Signed-off-by: Lennart Jern <lennart.jern@est.tech>
2ade793
to
3bbfb67
Compare
/test metal3-bmo-e2e-test-pull |
/lgtm |
/test-centos-e2e-integration-main |
What this PR does / why we need it:
This adds the trigger phrases for the e2e tests to the README.md and also the build badge for the periodic job.
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged):Fixes #