E2E Tests: Enable client-side media processing for site editor image test#76648
Conversation
…test Remove the `gutenberg-test-plugin-disable-client-side-media-processing` workaround from the "Image - Site editor" test. The upload pipeline issue that originally required this workaround (items getting stuck in the upload-media store queue) has been resolved by subsequent improvements to the upload pipeline. The test now runs with client-side media processing enabled and passes reliably, matching the behavior of the post editor image tests. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
|
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: 8.76 MB ℹ️ View Unchanged
|
|
Flaky tests detected in 36ee5b8. 🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/23265526994
|
andrewserong
left a comment
There was a problem hiding this comment.
LGTM, e2es are passing locally and in the Github Actions ![]()
| await expect( image ).toHaveAttribute( 'src', /\/[^\s]+\.\w+$/i, { | ||
| // Wait for upload to complete (includes client-side media processing time). | ||
| // With client-side processing, the filename may be changed by the server. | ||
| await expect( image ).toHaveAttribute( 'src', /^https?:\/\//, { |
There was a problem hiding this comment.
This change looks good to me, I assume all we're really wanting to test is that we have a real url now instead of a blob 👍
…test (#76648) Remove the `gutenberg-test-plugin-disable-client-side-media-processing` workaround from the "Image - Site editor" test. The upload pipeline issue that originally required this workaround (items getting stuck in the upload-media store queue) has been resolved by subsequent improvements to the upload pipeline. The test now runs with client-side media processing enabled and passes reliably, matching the behavior of the post editor image tests. Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
…test (#76648) Remove the `gutenberg-test-plugin-disable-client-side-media-processing` workaround from the "Image - Site editor" test. The upload pipeline issue that originally required this workaround (items getting stuck in the upload-media store queue) has been resolved by subsequent improvements to the upload pipeline. The test now runs with client-side media processing enabled and passes reliably, matching the behavior of the post editor image tests. Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
…test (#76648) Remove the `gutenberg-test-plugin-disable-client-side-media-processing` workaround from the "Image - Site editor" test. The upload pipeline issue that originally required this workaround (items getting stuck in the upload-media store queue) has been resolved by subsequent improvements to the upload pipeline. The test now runs with client-side media processing enabled and passes reliably, matching the behavior of the post editor image tests. Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Summary
gutenberg-test-plugin-disable-client-side-media-processingworkaround from the "Image - Site editor" E2E testcore/upload-mediastore queue) has been resolved by subsequent improvements to the upload pipeline--repeat-each=3)Contributes to #74367
Test plan
npm run test:e2e -- test/e2e/specs/editor/blocks/image.spec.js --grep "Site editor"— should passnpm run test:e2e -- test/e2e/specs/editor/blocks/image.spec.js— all 23 image block tests should pass--repeat-each=3🤖 Generated with Claude Code