Query Block test inserting interactive and non-interactive blocks #61370
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
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. |
|
@cbravobernal Here's my first attempt at a playwright test following up on #60006. I'd be grateful for your feedback. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What?
Adds two tests for the query block inserting interactive and non-interactive blocks inside a query block set to interactive mode.
Why?
With the release of the interactivity api users can add non-core blocks to the query block in interactive mode. These test will ensure we always check that the inserted block is compatible with interactive mode. This is a follow up to #60006
How?
Adds two tests, inserting a interactive and a non-interactive block (core/shortcode)
Testing Instructions
npm run test:e2e -- test/e2e/specs/editor/blocks/query.specAll tests should pass.