Automated Testing: Merge reports into HTML artifact#75633
Conversation
|
The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message. To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
|
Size Change: 0 B Total Size: 6.84 MB ℹ️ View Unchanged
|
342ce35 to
969b53c
Compare
969b53c to
e12f8a9
Compare
youknowriad
left a comment
There was a problem hiding this comment.
I'm not one who looks too much into these reports but if it helps you, why not 👍
|
Thanks, @youknowriad! Yeah, I think it could be helpful for debugging/profiling e2e tests. Similar to the current artifacts we have on trunk. Sidenote: I'm also wondering if we can use new AI tooling from GitHub/Playwright to debug/fix our flaky test reports. They often get neglected. |
What?
PR aims to improve artifacts generated by Playwright by consolidating all data into a single report. The HTML reporter received nice updates recently, such as "Speedboard".
I think a new report system would help us better monitor our e2e tests.
P.S. This is a first pass to see how it could affect our CI runs.
Testing Instructions
Screenshot