-
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
Block Visibility: Add e2e test #65880
Conversation
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 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. |
Size Change: 0 B Total Size: 1.77 MB ℹ️ View Unchanged
|
I really appreciate the follow-up @t-hamano I should have done so myself :P |
Flaky tests detected in 2fe53a6. 🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/11189198871
|
* Block Visibility: Add e2e test * Use `toHaveCount` instead of `toBe` Co-authored-by: t-hamano <[email protected]> Co-authored-by: Mamaduka <[email protected]> Co-authored-by: youknowriad <[email protected]>
Part of this comment: #62703 (comment)
What?
Add e2e test for the "Manage block visibility" setting
Why?
I think we need to make the
BlockManager
component reusable to implement UI for allowedBlocks, but before that, we need E2E tests to prevent unintended regressions.How
I have tested the basic functionality, but if there is anything else I should test, please let me know.
Testing Instructions
Run one of the following codes: