-
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
"Multiple use" block validation logic improvement [with Playwright] #57576
"Multiple use" block validation logic improvement [with Playwright] #57576
Conversation
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.
Thank you, @fai-sal!
The correct directory for Playwright e2e tests is test/e2e/specs/editor/various
.
I also would recommend checking the project e2e test best practices documentation - https://developer.wordpress.org/block-editor/contributors/code/testing-overview/e2e/#best-practices.
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.
Appreciate all your hard work here 🙇
The e2e tests will need to be rewritten to utilise Playwright APIs such as getByRole
.
A lot of the await will be able to be removed as well. You should find it's a lot easier to author the tests as well.
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.
Thanks for migrating to Playwright. A few comments about the test selectors 🙏
Hi @getdave, If you can allocate some time, can you please review the PR again. Thanks 🙇 |
I think we should look to land this in time for WP 6.5. I've put it on the board for that project which should ensure a number of 👀 on it. |
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.
Left a few nits but this looks good to me.
Co-authored-by: Ben Dwyer <[email protected]>
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 Unlinked AccountsThe following contributors have not linked their GitHub and WordPress.org accounts: @ihdk. Contributors, please read how to link your accounts to ensure your work is properly credited in WordPress releases. 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. |
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.
Let's bring this in. Thank you for the persistence here 🙇
Why
What
Co-authored-by: getdave [email protected]
Co-authored-by: Mamaduka [email protected]
Co-authored-by: scruffian [email protected]