-
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
Navigation: e2e tests: default to my only existing menu #47744
Conversation
Size Change: 0 B Total Size: 1.32 MB ℹ️ View Unchanged
|
Flaky tests detected in 2578dfa. 🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/4125536262
|
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.
Nice work! Just some minor suggestions.
4f75756
to
d49a247
Compare
Ok this should be ready for another review, and hope the tests pass. |
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.
LGTM 👍. Just some small suggestions left but they shouldn't be blocking 💯 . Thanks a lot!
Co-authored-by: Kai Hao <[email protected]>
c39ac92
to
6e73320
Compare
Thank you so much for your help with this @kevin940726 !! I learned a lot from your review. |
What?
This is part of the effort to re work all the navigation block e2e tests and migration to playwright. This is one of the user stories described in #45199
This test checks that when only one navigation menu exists, inserting a Navigation block will default correctly to using said menu.
Testing Instructions
Run npm run test:e2e:playwright -- editor/blocks/navigation.spec.js