Include boost in Jetpack #91660
haqadne2e-tests.yml
on: pull_request
Annotations
17 errors and 7 notices
|
Jetpack Boost - Modules e2e tests
TimeoutError: locator.waitFor: Timeout 20000ms exceeded.
Call log:
- waiting for locator('[data-testid="speed-scores"]').first() to be visible
at ../../../../../tools/e2e-commons/pages/page-actions.js:320
318 | );
319 | const element = this.page.locator( selector ).first();
> 320 | await element.waitFor( { state, timeout } );
| ^
321 | return element;
322 | }
323 |
at JetpackBoostPage.waitForElementState (/home/runner/work/jetpack/jetpack/tools/e2e-commons/pages/page-actions.js:320:17)
at JetpackBoostPage.waitForElementToBeVisible (/home/runner/work/jetpack/jetpack/tools/e2e-commons/pages/page-actions.js:269:21)
at JetpackBoostPage.chooseFreePlan (/home/runner/work/jetpack/jetpack/projects/plugins/boost/tests/e2e/lib/pages/wp-admin/JetpackBoostPage.js:21:14)
at connect (/home/runner/work/jetpack/jetpack/projects/plugins/boost/tests/e2e/lib/env/prerequisites.js:169:2)
at ensureConnectedState (/home/runner/work/jetpack/jetpack/projects/plugins/boost/tests/e2e/lib/env/prerequisites.js:158:3)
at buildPrerequisites (/home/runner/work/jetpack/jetpack/projects/plugins/boost/tests/e2e/lib/env/prerequisites.js:82:5)
at Object.build (/home/runner/work/jetpack/jetpack/projects/plugins/boost/tests/e2e/lib/env/prerequisites.js:59:4)
at default (/home/runner/work/jetpack/jetpack/projects/plugins/boost/tests/e2e/lib/setupTests.js:9:2)
|
|
Jetpack Boost - Modules e2e tests
Process completed with exit code 1.
|
|
Jetpack Boost - Base e2e tests
TimeoutError: locator.waitFor: Timeout 20000ms exceeded.
Call log:
- waiting for locator('[data-testid="speed-scores"]').first() to be visible
at ../../../../../tools/e2e-commons/pages/page-actions.js:320
318 | );
319 | const element = this.page.locator( selector ).first();
> 320 | await element.waitFor( { state, timeout } );
| ^
321 | return element;
322 | }
323 |
at JetpackBoostPage.waitForElementState (/home/runner/work/jetpack/jetpack/tools/e2e-commons/pages/page-actions.js:320:17)
at JetpackBoostPage.waitForElementToBeVisible (/home/runner/work/jetpack/jetpack/tools/e2e-commons/pages/page-actions.js:269:21)
at JetpackBoostPage.chooseFreePlan (/home/runner/work/jetpack/jetpack/projects/plugins/boost/tests/e2e/lib/pages/wp-admin/JetpackBoostPage.js:21:14)
at connect (/home/runner/work/jetpack/jetpack/projects/plugins/boost/tests/e2e/lib/env/prerequisites.js:169:2)
at ensureConnectedState (/home/runner/work/jetpack/jetpack/projects/plugins/boost/tests/e2e/lib/env/prerequisites.js:158:3)
at buildPrerequisites (/home/runner/work/jetpack/jetpack/projects/plugins/boost/tests/e2e/lib/env/prerequisites.js:82:5)
at Object.build (/home/runner/work/jetpack/jetpack/projects/plugins/boost/tests/e2e/lib/env/prerequisites.js:59:4)
at default (/home/runner/work/jetpack/jetpack/projects/plugins/boost/tests/e2e/lib/setupTests.js:9:2)
|
|
Jetpack Boost - Base e2e tests
Process completed with exit code 1.
|
|
Jetpack Boost - Image CDN e2e tests
TimeoutError: locator.waitFor: Timeout 20000ms exceeded.
Call log:
- waiting for locator('[data-testid="speed-scores"]').first() to be visible
at ../../../../../tools/e2e-commons/pages/page-actions.js:320
318 | );
319 | const element = this.page.locator( selector ).first();
> 320 | await element.waitFor( { state, timeout } );
| ^
321 | return element;
322 | }
323 |
at JetpackBoostPage.waitForElementState (/home/runner/work/jetpack/jetpack/tools/e2e-commons/pages/page-actions.js:320:17)
at JetpackBoostPage.waitForElementToBeVisible (/home/runner/work/jetpack/jetpack/tools/e2e-commons/pages/page-actions.js:269:21)
at JetpackBoostPage.chooseFreePlan (/home/runner/work/jetpack/jetpack/projects/plugins/boost/tests/e2e/lib/pages/wp-admin/JetpackBoostPage.js:21:14)
at connect (/home/runner/work/jetpack/jetpack/projects/plugins/boost/tests/e2e/lib/env/prerequisites.js:169:2)
at ensureConnectedState (/home/runner/work/jetpack/jetpack/projects/plugins/boost/tests/e2e/lib/env/prerequisites.js:158:3)
at buildPrerequisites (/home/runner/work/jetpack/jetpack/projects/plugins/boost/tests/e2e/lib/env/prerequisites.js:82:5)
at Object.build (/home/runner/work/jetpack/jetpack/projects/plugins/boost/tests/e2e/lib/env/prerequisites.js:59:4)
at default (/home/runner/work/jetpack/jetpack/projects/plugins/boost/tests/e2e/lib/setupTests.js:9:2)
|
|
Jetpack Boost - Image CDN e2e tests
Process completed with exit code 1.
|
|
Jetpack Boost - Concatenate JS/CSS e2e tests
The artifact name is not valid: test-output-Jetpack Boost - Concatenate JS/CSS. Contains the following character: Forward slash /
Invalid characters include: Double quote ", Colon :, Less than <, Greater than >, Vertical bar |, Asterisk *, Question mark ?, Carriage return \r, Line feed \n, Backslash \, Forward slash /
These characters are not allowed in the artifact name due to limitations with certain file systems such as NTFS. To maintain file system agnostic behavior, these characters are intentionally not allowed to prevent potential problems with downloads on different file systems.
|
|
specs/critical-css/critical-css.test.js:60:2 › Critical CSS module › Critical CSS meta information should show on the admin when the module is re-activated:
projects/plugins/boost/tests/e2e/specs/critical-css/critical-css.test.js#L1
1) specs/critical-css/critical-css.test.js:60:2 › Critical CSS module › Critical CSS meta information should show on the admin when the module is re-activated
Test timeout of 300000ms exceeded.
|
|
specs/critical-css/critical-css.test.js:60:2 › Critical CSS module › Critical CSS meta information should show on the admin when the module is re-activated:
tools/e2e-commons/pages/page-actions.js#L43
1) specs/critical-css/critical-css.test.js:60:2 › Critical CSS module › Critical CSS meta information should show on the admin when the module is re-activated
Error: page.goto: Target page, context or browser has been closed
at ../../../../../tools/e2e-commons/pages/page-actions.js:43
41 | } catch ( e ) {
42 | logger.error( `Error navigating to ${ url } (1). Retrying once.\n${ e }` );
> 43 | response = await this.page.goto( url, options );
| ^
44 | }
45 |
46 | return response;
at JetpackBoostPage.goto (/home/runner/work/jetpack/jetpack/tools/e2e-commons/pages/page-actions.js:43:31)
at Function.visit (/home/runner/work/jetpack/jetpack/tools/e2e-commons/pages/wp-page.js:31:3)
at /home/runner/work/jetpack/jetpack/projects/plugins/boost/tests/e2e/specs/critical-css/critical-css.test.js:63:28
|
|
specs/critical-css/critical-css.test.js:60:2 › Critical CSS module › Critical CSS meta information should show on the admin when the module is re-activated:
tools/e2e-commons/pages/page-actions.js#L320
1) specs/critical-css/critical-css.test.js:60:2 › Critical CSS module › Critical CSS meta information should show on the admin when the module is re-activated
Retry #1 ───────────────────────────────────────────────────────────────────────────────────────
TimeoutError: locator.waitFor: Timeout 20000ms exceeded.
Call log:
- waiting for locator('#jb-dashboard').first() to be visible
at ../../../../../tools/e2e-commons/pages/page-actions.js:320
318 | );
319 | const element = this.page.locator( selector ).first();
> 320 | await element.waitFor( { state, timeout } );
| ^
321 | return element;
322 | }
323 |
at JetpackBoostPage.waitForElementState (/home/runner/work/jetpack/jetpack/tools/e2e-commons/pages/page-actions.js:320:17)
at JetpackBoostPage.waitForElementToBeVisible (/home/runner/work/jetpack/jetpack/tools/e2e-commons/pages/page-actions.js:269:21)
at JetpackBoostPage.waitForPage (/home/runner/work/jetpack/jetpack/tools/e2e-commons/pages/page-actions.js:67:16)
at Function.init (/home/runner/work/jetpack/jetpack/tools/e2e-commons/pages/wp-page.js:18:3)
at /home/runner/work/jetpack/jetpack/projects/plugins/boost/tests/e2e/specs/critical-css/critical-css.test.js:63:28
|
|
specs/critical-css/critical-css.test.js:70:2 › Critical CSS module › Critical CSS should be available on the frontend when the module is active:
projects/plugins/boost/tests/e2e/specs/critical-css/critical-css.test.js#L72
2) specs/critical-css/critical-css.test.js:70:2 › Critical CSS module › Critical CSS should be available on the frontend when the module is active
TimeoutError: locator.innerText: Timeout 20000ms exceeded.
Call log:
- waiting for locator('#jetpack-boost-critical-css')
70 | test( 'Critical CSS should be available on the frontend when the module is active', async () => {
71 | await PostFrontendPage.visit( page );
> 72 | const criticalCss = await page.locator( '#jetpack-boost-critical-css' ).innerText();
| ^
73 | expect( criticalCss.length, 'Critical CSS should be displayed' ).toBeGreaterThan( 100 );
74 | } );
75 |
at /home/runner/work/jetpack/jetpack/projects/plugins/boost/tests/e2e/specs/critical-css/critical-css.test.js:72:75
|
|
specs/critical-css/critical-css.test.js:70:2 › Critical CSS module › Critical CSS should be available on the frontend when the module is active:
projects/plugins/boost/tests/e2e/specs/critical-css/critical-css.test.js#L72
2) specs/critical-css/critical-css.test.js:70:2 › Critical CSS module › Critical CSS should be available on the frontend when the module is active
Retry #1 ───────────────────────────────────────────────────────────────────────────────────────
TimeoutError: locator.innerText: Timeout 20000ms exceeded.
Call log:
- waiting for locator('#jetpack-boost-critical-css')
70 | test( 'Critical CSS should be available on the frontend when the module is active', async () => {
71 | await PostFrontendPage.visit( page );
> 72 | const criticalCss = await page.locator( '#jetpack-boost-critical-css' ).innerText();
| ^
73 | expect( criticalCss.length, 'Critical CSS should be displayed' ).toBeGreaterThan( 100 );
74 | } );
75 |
at /home/runner/work/jetpack/jetpack/projects/plugins/boost/tests/e2e/specs/critical-css/critical-css.test.js:72:75
|
|
specs/critical-css/critical-css.test.js:76:2 › Critical CSS module › Critical CSS Admin message should show when the theme is changed:
tools/e2e-commons/pages/page-actions.js#L320
3) specs/critical-css/critical-css.test.js:76:2 › Critical CSS module › Critical CSS Admin message should show when the theme is changed
TimeoutError: locator.waitFor: Timeout 20000ms exceeded.
Call log:
- waiting for locator('#dashboard-widgets-wrap').first() to be visible
at ../../../../../tools/e2e-commons/pages/page-actions.js:320
318 | );
319 | const element = this.page.locator( selector ).first();
> 320 | await element.waitFor( { state, timeout } );
| ^
321 | return element;
322 | }
323 |
at DashboardPage.waitForElementState (/home/runner/work/jetpack/jetpack/tools/e2e-commons/pages/page-actions.js:320:17)
at DashboardPage.waitForElementToBeVisible (/home/runner/work/jetpack/jetpack/tools/e2e-commons/pages/page-actions.js:269:21)
at DashboardPage.waitForPage (/home/runner/work/jetpack/jetpack/tools/e2e-commons/pages/page-actions.js:67:16)
at Function.init (/home/runner/work/jetpack/jetpack/tools/e2e-commons/pages/wp-page.js:18:3)
at /home/runner/work/jetpack/jetpack/projects/plugins/boost/tests/e2e/specs/critical-css/critical-css.test.js:78:3
|
|
specs/critical-css/critical-css.test.js:76:2 › Critical CSS module › Critical CSS Admin message should show when the theme is changed:
tools/e2e-commons/pages/page-actions.js#L320
3) specs/critical-css/critical-css.test.js:76:2 › Critical CSS module › Critical CSS Admin message should show when the theme is changed
Retry #1 ───────────────────────────────────────────────────────────────────────────────────────
TimeoutError: locator.waitFor: Timeout 20000ms exceeded.
Call log:
- waiting for locator('#dashboard-widgets-wrap').first() to be visible
at ../../../../../tools/e2e-commons/pages/page-actions.js:320
318 | );
319 | const element = this.page.locator( selector ).first();
> 320 | await element.waitFor( { state, timeout } );
| ^
321 | return element;
322 | }
323 |
at DashboardPage.waitForElementState (/home/runner/work/jetpack/jetpack/tools/e2e-commons/pages/page-actions.js:320:17)
at DashboardPage.waitForElementToBeVisible (/home/runner/work/jetpack/jetpack/tools/e2e-commons/pages/page-actions.js:269:21)
at DashboardPage.waitForPage (/home/runner/work/jetpack/jetpack/tools/e2e-commons/pages/page-actions.js:67:16)
at Function.init (/home/runner/work/jetpack/jetpack/tools/e2e-commons/pages/wp-page.js:18:3)
at /home/runner/work/jetpack/jetpack/projects/plugins/boost/tests/e2e/specs/critical-css/critical-css.test.js:78:3
|
|
specs/critical-css/critical-css.test.js:101:2 › Critical CSS module › Critical CSS should be generated with an error (advanced recommendations):
tools/e2e-commons/pages/page-actions.js#L320
4) specs/critical-css/critical-css.test.js:101:2 › Critical CSS module › Critical CSS should be generated with an error (advanced recommendations)
TimeoutError: locator.waitFor: Timeout 20000ms exceeded.
Call log:
- waiting for locator('#jb-dashboard').first() to be visible
at ../../../../../tools/e2e-commons/pages/page-actions.js:320
318 | );
319 | const element = this.page.locator( selector ).first();
> 320 | await element.waitFor( { state, timeout } );
| ^
321 | return element;
322 | }
323 |
at JetpackBoostPage.waitForElementState (/home/runner/work/jetpack/jetpack/tools/e2e-commons/pages/page-actions.js:320:17)
at JetpackBoostPage.waitForElementToBeVisible (/home/runner/work/jetpack/jetpack/tools/e2e-commons/pages/page-actions.js:269:21)
at JetpackBoostPage.waitForPage (/home/runner/work/jetpack/jetpack/tools/e2e-commons/pages/page-actions.js:67:16)
at Function.init (/home/runner/work/jetpack/jetpack/tools/e2e-commons/pages/wp-page.js:18:3)
at /home/runner/work/jetpack/jetpack/projects/plugins/boost/tests/e2e/specs/critical-css/critical-css.test.js:117:28
|
|
specs/critical-css/critical-css.test.js:101:2 › Critical CSS module › Critical CSS should be generated with an error (advanced recommendations):
tools/e2e-commons/pages/page-actions.js#L320
4) specs/critical-css/critical-css.test.js:101:2 › Critical CSS module › Critical CSS should be generated with an error (advanced recommendations)
Retry #1 ───────────────────────────────────────────────────────────────────────────────────────
TimeoutError: locator.waitFor: Timeout 20000ms exceeded.
Call log:
- waiting for locator('#jb-dashboard').first() to be visible
at ../../../../../tools/e2e-commons/pages/page-actions.js:320
318 | );
319 | const element = this.page.locator( selector ).first();
> 320 | await element.waitFor( { state, timeout } );
| ^
321 | return element;
322 | }
323 |
at JetpackBoostPage.waitForElementState (/home/runner/work/jetpack/jetpack/tools/e2e-commons/pages/page-actions.js:320:17)
at JetpackBoostPage.waitForElementToBeVisible (/home/runner/work/jetpack/jetpack/tools/e2e-commons/pages/page-actions.js:269:21)
at JetpackBoostPage.waitForPage (/home/runner/work/jetpack/jetpack/tools/e2e-commons/pages/page-actions.js:67:16)
at Function.init (/home/runner/work/jetpack/jetpack/tools/e2e-commons/pages/wp-page.js:18:3)
at /home/runner/work/jetpack/jetpack/projects/plugins/boost/tests/e2e/specs/critical-css/critical-css.test.js:117:28
|
|
specs/critical-css/critical-css.test.js:132:2 › Critical CSS module › User can access the Critical advanced recommendations and go back to settings page:
tools/e2e-commons/pages/page-actions.js#L320
5) specs/critical-css/critical-css.test.js:132:2 › Critical CSS module › User can access the Critical advanced recommendations and go back to settings page
TimeoutError: locator.waitFor: Timeout 20000ms exceeded.
Call log:
- waiting for locator('#jb-dashboard').first() to be visible
at ../../../../../tools/e2e-commons/pages/page-actions.js:320
318 | );
319 | const element = this.page.locator( selector ).first();
> 320 | await element.waitFor( { state, timeout } );
| ^
321 | return element;
322 | }
323 |
at JetpackBoostPage.waitForElementState (/home/runner/work/jetpack/jetpack/tools/e2e-commons/pages/page-actions.js:320:17)
at JetpackBoostPage.waitForElementToBeVisible (/home/runner/work/jetpack/jetpack/tools/e2e-commons/pages/page-actions.js:269:21)
at JetpackBoostPage.waitForPage (/home/runner/work/jetpack/jetpack/tools/e2e-commons/pages/page-actions.js:67:16)
at Function.init (/home/runner/work/jetpack/jetpack/tools/e2e-commons/pages/wp-page.js:18:3)
at /home/runner/work/jetpack/jetpack/projects/plugins/boost/tests/e2e/specs/critical-css/critical-css.test.js:135:28
|
|
🎭 Playwright Run Summary
1 passed (37.4s)
|
|
🎭 Playwright Run Summary
2 passed (44.9s)
|
|
🎭 Playwright Run Summary
5 passed (1.2m)
|
|
🎭 Playwright Run Summary
5 passed (1.2m)
|
|
🎭 Playwright Run Summary
2 passed (2.1m)
|
|
🎭 Playwright Run Summary
2 passed (3.3m)
|
|
🎭 Playwright Run Summary
5 failed
specs/critical-css/critical-css.test.js:60:2 › Critical CSS module › Critical CSS meta information should show on the admin when the module is re-activated
specs/critical-css/critical-css.test.js:70:2 › Critical CSS module › Critical CSS should be available on the frontend when the module is active
specs/critical-css/critical-css.test.js:76:2 › Critical CSS module › Critical CSS Admin message should show when the theme is changed
specs/critical-css/critical-css.test.js:101:2 › Critical CSS module › Critical CSS should be generated with an error (advanced recommendations)
specs/critical-css/critical-css.test.js:132:2 › Critical CSS module › User can access the Critical advanced recommendations and go back to settings page
3 passed (10.6m)
|
Artifacts
Produced during runtime
| Name | Size | |
|---|---|---|
|
test-output-Jetpack Boost - Base
Expired
|
2.98 KB |
|
|
test-output-Jetpack Boost - Critical CSS
Expired
|
76.7 KB |
|
|
test-output-Jetpack Boost - Image CDN
Expired
|
2.98 KB |
|
|
test-output-Jetpack Boost - Image Guide
Expired
|
7.45 KB |
|
|
test-output-Jetpack Boost - Modules
Expired
|
2.98 KB |
|
|
test-output-Jetpack Boost - Page Cache
Expired
|
12.5 KB |
|
|
test-output-Jetpack connection
Expired
|
12.5 KB |
|
|
test-output-Jetpack post-connection
Expired
|
16.4 KB |
|
|
test-output-Jetpack pre-connection
Expired
|
7.28 KB |
|