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
E2E Tests: Disable access to remote block directory and patterns #12935
Conversation
They often cause block validation console errors on older WordPress version
4ef36ad
to
272629e
Compare
Plugin builds for cf17809 are ready 🛎️!
|
Size Change: 0 B Total Size: 2.71 MB ℹ️ View Unchanged
|
@spacedmonkey FYI, removed Airplane Mode again because it caused too many tests to fail, for example around media hotlinking or when using the AMP CDN (Web Stories block, AMP validator) |
@@ -41,7 +41,7 @@ | |||
* | |||
* @param bool $network_wide Whether to activate network-wide. | |||
*/ | |||
function activate( bool $network_wide = false ): void { | |||
function activate( ?bool $network_wide = false ): void { |
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.
Changed this because it's not always a bool, e.g. when activating a plugin via WP-CLI.
'<rootDir>/packages/e2e-tests/node_modules/@wordpress/jest-puppeteer-axe', | ||
'<rootDir>/packages/e2e-tests/node_modules/@wordpress/jest-console', |
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.
Since these packages are not always in the node_modules
folder in the root folder (because of npm workspaces), this is the way.
Those timeouts are not great 😕 No idea why tests suddenly take that long... |
Timeout is not resolved yet, but merging to unblock other PRs. |
Context
They often cause block validation console errors on older WordPress version. This currently causes our e2e tests against WP 5.9 to fail.
Summary
Disable access to remote block directory and patterns
Relevant Technical Choices
To-do
User-facing changes
Testing Instructions
This PR can be tested by following these steps:
Reviews
Does this PR have a security-related impact?
Does this PR change what data or activity we track or use?
Does this PR have a legal-related impact?
Checklist
Type: XYZ
label to the PRFixes #