Image editor: improve media editor crop accessibility and dialog focu… #154285
Annotations
6 errors and 8 notices
|
[chromium] › specs/interactivity/router-regions.spec.ts:543:6 › Router regions › should be preserved on first navigation with `data-wp-key` and `attachTo`:
test/e2e/specs/interactivity/router-regions.spec.ts#L585
2) [chromium] › specs/interactivity/router-regions.spec.ts:543:6 › Router regions › should be preserved on first navigation with `data-wp-key` and `attachTo`
Error: expect(locator).toHaveText(expected) failed
Locator: getByTestId('region-1-ssr')
Expected: "content from page attachTo2"
Received: "content from page 1"
Timeout: 5000ms
Call log:
- Expect "toHaveText" with timeout 5000ms
- waiting for getByTestId('region-1-ssr')
2 × locator resolved to <p data-testid="region-1-ssr">content from page attachTo1</p>
- unexpected value "content from page attachTo1"
7 × locator resolved to <p data-testid="region-1-ssr">content from page 1</p>
- unexpected value "content from page 1"
583 | // Navigate to "Page attachTo 2".
584 | await page.getByTestId( 'next' ).click();
> 585 | await expect( region1Ssr ).toHaveText( 'content from page attachTo2' );
| ^
586 |
587 | // Regions with `data-wp-key` and other directives should not be recreated.
588 | for ( const regionId in regions ) {
at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/interactivity/router-regions.spec.ts:585:30
|
|
[chromium] › specs/interactivity/router-navigate.spec.ts:67:6 › Router navigate › should update the HTML only for the latest navigation:
test/e2e/specs/interactivity/router-navigate.spec.ts#L100
1) [chromium] › specs/interactivity/router-navigate.spec.ts:67:6 › Router navigate › should update the HTML only for the latest navigation
TypeError: resolveLink2 is not a function
98 | await expect( title ).toHaveText( 'Main' );
99 |
> 100 | await Promise.resolve().then( () => resolveLink2() );
| ^
101 |
102 | await expect( navigations ).toHaveText( '1' );
103 | await expect( status ).toHaveText( 'busy' );
at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/interactivity/router-navigate.spec.ts:100:39
at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/interactivity/router-navigate.spec.ts:100:3
|
|
[chromium] › specs/site-editor/homepage-settings.spec.js:62:2 › Homepage Settings via Editor › should show correct homepage actions based on current homepage or posts page:
test/e2e/specs/site-editor/homepage-settings.spec.js#L93
1) [chromium] › specs/site-editor/homepage-settings.spec.js:62:2 › Homepage Settings via Editor › should show correct homepage actions based on current homepage or posts page
Error: locator.click: Error: strict mode violation: getByRole('row').filter({ has: getByRole('gridcell').getByLabel('Sample page') }) resolved to 2 elements:
1) <div class="" id=":ru:" role="row">…</div> aka getByRole('row', { name: 'Sample Page Edit Actions Author Author avatar admin Status Published', exact: true })
2) <div class="" id=":r16:" role="row">…</div> aka getByRole('row', { name: 'Sample page Edit Actions Author Author avatar admin Status Published', exact: true })
Call log:
- waiting for getByRole('row').filter({ has: getByRole('gridcell').getByLabel('Sample page') })
91 | .filter( { has: samplePageTwo } );
92 | // eslint-disable-next-line playwright/no-force-option
> 93 | await samplePageTwoRow.click( { force: true } );
| ^
94 | await samplePageTwoRow
95 | .getByRole( 'button', {
96 | name: 'Actions',
at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/site-editor/homepage-settings.spec.js:93:26
|
|
[chromium] › specs/editor/various/post-content-focus-mode.spec.js:129:3 › Post Content focus mode › post content inside a template part › post title and content are editable and blocks can be inserted:
packages/e2e-test-utils-playwright/src/editor/select-blocks.ts#L26
1) [chromium] › specs/editor/various/post-content-focus-mode.spec.js:129:3 › Post Content focus mode › post content inside a template part › post title and content are editable and blocks can be inserted › Paragraph and Group blocks are available in the inserter
TimeoutError: locator.getAttribute: Timeout 10000ms exceeded.
Call log:
- waiting for locator('[name="editor-canvas"]').contentFrame().getByText('Initial content')
at ../../../packages/e2e-test-utils-playwright/src/editor/select-blocks.ts:26
24 | : endSelectorOrLocator;
25 |
> 26 | const startClientId = await startBlock.getAttribute( 'data-block' );
| ^
27 | const endClientId = await endBlock?.getAttribute( 'data-block' );
28 |
29 | if ( endClientId ) {
at Editor.selectBlocks (/home/runner/work/gutenberg/gutenberg/packages/e2e-test-utils-playwright/src/editor/select-blocks.ts:26:41)
at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/various/post-content-focus-mode.spec.js:163:18
at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/various/post-content-focus-mode.spec.js:159:15
|
|
[chromium] › specs/admin/font-library.spec.js:32:3 › Font Library › When a user manages custom fonts via the UI › should allow user to add and remove multiple local font files:
test/e2e/specs/admin/font-library.spec.js#L61
1) [chromium] › specs/admin/font-library.spec.js:32:3 › Font Library › When a user manages custom fonts via the UI › should allow user to add and remove multiple local font files
Error: expect(locator).toBeVisible() failed
Locator: getByLabel('Exo 2 Semi-bold Italic')
Expected: visible
Timeout: 5000ms
Error: element(s) not found
Call log:
- Expect "toBeVisible" with timeout 5000ms
- waiting for getByLabel('Exo 2 Semi-bold Italic')
59 | await expect(
60 | page.getByLabel( 'Exo 2 Semi-bold Italic' )
> 61 | ).toBeVisible();
| ^
62 |
63 | // Check CSS preset was created by creating a post and applying the font.
64 | await admin.createNewPost();
at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/admin/font-library.spec.js:61:6
|
|
Report to GitHub
HttpError: Resource not accessible by integration
|
|
🎭 Playwright Run Summary
2 flaky
[chromium] › specs/interactivity/router-navigate.spec.ts:67:6 › Router navigate › should update the HTML only for the latest navigation
[chromium] › specs/interactivity/router-regions.spec.ts:543:6 › Router regions › should be preserved on first navigation with `data-wp-key` and `attachTo`
7 skipped
245 passed (9.5m)
|
|
🎭 Playwright Run Summary
1 flaky
[chromium] › specs/site-editor/homepage-settings.spec.js:62:2 › Homepage Settings via Editor › should show correct homepage actions based on current homepage or posts page
3 skipped
251 passed (12.2m)
|
|
🎭 Playwright Run Summary
1 flaky
[chromium] › specs/editor/various/post-content-focus-mode.spec.js:129:3 › Post Content focus mode › post content inside a template part › post title and content are editable and blocks can be inserted
5 skipped
233 passed (12.6m)
|
|
🎭 Playwright Run Summary
4 skipped
263 passed (13.6m)
|
|
🎭 Playwright Run Summary
1 flaky
[chromium] › specs/admin/font-library.spec.js:32:3 › Font Library › When a user manages custom fonts via the UI › should allow user to add and remove multiple local font files
253 passed (14.1m)
|
|
🎭 Playwright Run Summary
6 skipped
247 passed (17.5m)
|
|
🎭 Playwright Run Summary
13 skipped
243 passed (13.3m)
|
|
🎭 Playwright Run Summary
1 skipped
253 passed (24.8m)
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
blob-reports-merged
|
10.7 MB |
sha256:59e330d9fd5550ddc70b6a33c94412ecfc5da3294cccb134951196863bfba5b6
|
|
|
flaky-tests-report
|
5.44 KB |
sha256:8f2b826d8d8578b59e70cbe4218b9d9f6ca64fa1f32e7e5560e2811066f3a72e
|
|
|
html-report--attempt-1
|
10.2 MB |
sha256:5a08faf45adaff16f559f1e113139b788fdce432d872f309856d274b810869dd
|
|