-
Notifications
You must be signed in to change notification settings - Fork 367
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
test: [M3-6876] - Improve formatting of GitHub test result comments #11200
test: [M3-6876] - Improve formatting of GitHub test result comments #11200
Conversation
This reverts commit 868bafb.
Coverage Report: ✅ |
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.
Nice, thank you!
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.
awesome, thanks Joe! 🎉
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.
The formatting improvements LGTM 🎉
Cloud Manager E2E Run #6771
Run Properties:
|
Project |
Cloud Manager E2E
|
Branch Review |
develop
|
Run status |
Passed #6771
|
Run duration | 26m 42s |
Commit |
2e6defb927: test: [M3-6876] - Improve formatting of GitHub test result comments (#11200)
|
Committer | jdamore-linode |
View all properties for this run ↗︎ |
Test results | |
---|---|
Failures |
0
|
Flaky |
3
|
Pending |
2
|
Skipped |
0
|
Passing |
445
|
View all changes introduced in this branch ↗︎ |
Description 📝
This PR makes some slight improvements to our GitHub comment test result formatter script. It improves the formatting of the breakdown showing the number of passing, failing, and skipped tests, adds a customizable title, and changes the "Debugging" heading to "Troubleshooting".
Note that this is a low priority and our separate changes to enable GitHub Comments in CI do not rely on these changes being in place first.
Changes 🔄
Target release date 🗓️
N/A, this is not a high priority at all.
Preview 📷
Passing:
With Failures:
I didn't take any screenshots showing the before state, but the table showing the number of passing, failing, and skipped tests was previously a one liner along the lines of " ❌ N failing tests | 💚 N passing tests | 🔽 N skipped tests", and the "Cloud Manager UI Test Results" heading was not present.
How to test 🧪
You can manually run the
yarn junit:summary <path> --format github
command and validate its output, or check out the comments posted to my test PR on my fork: jdamore-linode#25Soon I'll add some links to Jenkins run to the Jira ticket showing how it all fits together.
As an Author I have considered 🤔
Check all that apply