-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
Migrate custom taxonomies test to Playwright #45178
Conversation
👋 Thanks for your first Pull Request and for helping build the future of Gutenberg and WordPress, @alvitazwar! In case you missed it, we'd love to have you join us in our Slack community, where we hold regularly weekly meetings open to anyone to coordinate with each other. If you want to learn more about WordPress development in general, check out the Core Handbook full of helpful information. |
@Mamaduka Can you please help me to review this PR? |
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.
@alvitazwar, let's do a similar refactoring for this test case as we did in #43964.
- Inline helper utility.
- Try to use role selectors whenever possible.
@Mamaduka I addressed the feedback regarding the inline approach and use of role selectors. Can you please check? |
@Mamaduka Can you please check again? |
@alvitazwar, can you rebase this branch on top of the latest trunk? It should resolve the issue with CI. |
* Refactor Site Editor code * Naming consistency
What?
Based on #38570, part of #38851. Migrate custom-taxonomies.test.js
Why?
See #38570 for its background and rationale.
This is split into a new PR for easier review.
How?
See #38570 for the proposed migration steps.
Testing Instructions
npm run test:e2e:playwright /test/e2e/specs/editor/plugins/custom-taxonomies.spec.js
Screenshots or screencast
Screen.Recording.2022-10-21.at.12.11.32.AM.mov