Clarify e2e test behavior with Gutenberg disabled #73438
Closed
+0
−0
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?
Addresses confusion about why e2e tests don't run when Gutenberg plugin is disabled.
Why?
The PR modifies
.wp-env.jsonto test WP trunk without Gutenberg ("plugins": []), but this prevents e2e tests from running since they require Gutenberg features to be present.How?
No code changes. Clarified in comments that e2e tests cannot run without Gutenberg loaded as a plugin.
The current configuration:
{ "core": "WordPress/WordPress", "plugins": [] }Creates a vanilla WordPress environment with no Gutenberg to test. E2e tests fail during setup or when attempting to access non-existent Gutenberg features.
To run e2e tests on WP trunk with Gutenberg:
{ "core": "WordPress/WordPress", "plugins": [ "." ] }Testing Instructions
N/A - Documentation clarification only.
Testing Instructions for Keyboard
N/A
Screenshots or screencast
N/A
💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.