-
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
Puppeteer tests: Try to fix failing tests related to notices in core #54452
Conversation
Size Change: 0 B Total Size: 1.52 MB ℹ️ View Unchanged
|
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.
Tests are passing! LGTM
Thanks 🙇🏻
Is there a timeline for merging this into core tests? I don't know the process for this, but it would be nice to get the core e2e tests passing again. |
Oh, good question! I didn't realise that the core tests use this package, but that makes sense now. I imagine it'll happen when the next JS packages update happens? Might be worth double-checking with the editor tech leads for 6.4. Just pinging @mikachan and @tellthemachines in case I've got it wrong there. |
Yup this change should go in with the package updates in WordPress/wordpress-develop#5262. |
Just to double check - should this PR be backported to the 16.7 RC, or do these changes need to be manually added to WordPress/wordpress-develop#5262? |
@mikachan no action needed here; according to the milestone and time of merge this PR should already be in 16.7 RC 🙂 |
What?
Try to fix failing Puppeteer tests.
Why?
In core, recent commits update how notices are displayed. It looks like these existing tests might be dependent on the order in which some CSS classes are output. I notice that in core, previously the order was "updated notice is-dismissible", but the order is now "notice is-dismissible updated".
For these Gutenberg tests, the order is not significant, and I think we might be able to use a single class of "notice" in this Xpath query... at least that's what I'm trying out here!
Notices in WP 6.3.1
Notices in 6.4 alpha
How?
Try making the Xpath query a little less specific to see if that pleases the tests.
Testing Instructions
See if puppeteer tests pass
Testing Instructions for Keyboard
Screenshots or screencast