-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
E2E: stabilize failing tests in trunk #29836
Conversation
Size Change: 0 B Total Size: 1.4 MB ℹ️ View Unchanged
|
Looking into the failure from Looks green after a second run but @ellatrix does the suite I'm seeing the cursor on the page title for the |
6bb60bd
to
2a3d9a7
Compare
This one is ready for review ✅ |
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.
Looks good and tests are passing 👍 👍
// 'button[aria-label="Add block"]' | ||
// ); | ||
// await appender.click(); | ||
const appender = await page.waitForSelector( |
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.
@gwwar Thanks for switching this back. I'm curious - did the underlying issue (with variations not being available) get fixed here, or did it fix itself?
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.
Maybe from the server-side piece landing? WordPress/wordpress-develop#1015 (comment)
I guess you resolved the multi select problem? |
@ellatrix it resolved itself with another run on CI, but I was curious if it was working for folks locally. |
What do you get as a result? I have a failure in |
I do too, it appears to be okay in CI somehow. Running locally, focus is set on the post title. |
Sounds like it could use a separate issue and further investigation. |
This PR fixes breaking E2E tests that are present in trunk. See example run
Having flakey/broken tests in trunk reduces confidence in tests. After verifying if it's a real breakage let's fix or disable them. If it's a tricky one to test, it's okay to skip, but then follow up with a more stable test.
Testing Instructions
Local and CI runs for this branch should be green: