-
Notifications
You must be signed in to change notification settings - Fork 4.7k
e2e: fix flaky tests for settings sidebar #74929
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
Conversation
|
Size Change: 0 B Total Size: 3.1 MB ℹ️ View Unchanged
|
|
Flaky tests detected in 93cb449. 🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/21331868275
|
|
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. |
SirLouen
left a comment
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.
✅ Reviewed and tested, looking good
|
Thanks for the fix, @t-hamano!
I was also looking into this on Friday. The following seems like a bug to me, so maybe we have to look into the Tab component. cc @WordPress/gutenberg-components |
Fixes #48878
What?
Fixes a recently flaky e2e test for the settings sidebar.
Example:
Why?
Looking at the log, it seems that
aria-selectedistruefor both tabs "Template" and "Block".Perhaps the moment the Block tab is selected instead of the Template tab, aria-selected becomes true for both tabs.
How?
Make the assertion more strict: instead of checking the selected tab text, check the selection state of each tab instead.
Testing Instructions
All CI checks should be ✅