Add/fix critical css e2e on interstitial #102662
Annotations
10 errors and 1 notice
|
Run Jetpack Boost - Critical CSS tests:
tools/e2e-commons/pages/page-actions.js#L320
1) [chromium] › specs/critical-css/critical-css.test.js:47:2 › Critical CSS module › Critical CSS should be generated when the module is active
TimeoutError: locator.waitFor: Timeout 20000ms exceeded.
Call log:
- waiting for locator('.jb-critical-css-progress').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.waitForCriticalCssGenerationProgressUIVisibility (/home/runner/work/jetpack/jetpack/projects/plugins/boost/tests/e2e/lib/pages/wp-admin/JetpackBoostPage.js:111:15)
at /home/runner/work/jetpack/jetpack/projects/plugins/boost/tests/e2e/specs/critical-css/critical-css.test.js:51:27
|
|
Run Jetpack Boost - Critical CSS tests:
tools/e2e-commons/pages/page-actions.js#L320
1) [chromium] › specs/critical-css/critical-css.test.js:47:2 › Critical CSS module › Critical CSS should be generated when the module is active
Retry #1 ───────────────────────────────────────────────────────────────────────────────────────
TimeoutError: locator.waitFor: Timeout 20000ms exceeded.
Call log:
- waiting for locator('.jb-critical-css-progress').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.waitForCriticalCssGenerationProgressUIVisibility (/home/runner/work/jetpack/jetpack/projects/plugins/boost/tests/e2e/lib/pages/wp-admin/JetpackBoostPage.js:111:15)
at /home/runner/work/jetpack/jetpack/projects/plugins/boost/tests/e2e/specs/critical-css/critical-css.test.js:51:27
|
|
Run Jetpack Boost - Critical CSS tests:
tools/e2e-commons/pages/page-actions.js#L320
1) [chromium] › specs/critical-css/critical-css.test.js:47:2 › Critical CSS module › Critical CSS should be generated when the module is active
Retry #2 ───────────────────────────────────────────────────────────────────────────────────────
TimeoutError: locator.waitFor: Timeout 20000ms exceeded.
Call log:
- waiting for locator('.jb-critical-css-progress').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.waitForCriticalCssGenerationProgressUIVisibility (/home/runner/work/jetpack/jetpack/projects/plugins/boost/tests/e2e/lib/pages/wp-admin/JetpackBoostPage.js:111:15)
at /home/runner/work/jetpack/jetpack/projects/plugins/boost/tests/e2e/specs/critical-css/critical-css.test.js:51:27
|
|
Run Jetpack Boost - Critical CSS tests:
tools/e2e-commons/pages/page-actions.js#L320
2) [chromium] › 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
TimeoutError: locator.waitFor: Timeout 180000ms exceeded.
Call log:
- waiting for locator('[data-testid="critical-css-meta"]').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.waitForCriticalCssMetaInfoVisibility (/home/runner/work/jetpack/jetpack/projects/plugins/boost/tests/e2e/lib/pages/wp-admin/JetpackBoostPage.js:106:15)
at /home/runner/work/jetpack/jetpack/projects/plugins/boost/tests/e2e/specs/critical-css/critical-css.test.js:65:27
|
|
Run Jetpack Boost - Critical CSS tests:
tools/e2e-commons/pages/page-actions.js#L320
2) [chromium] › 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 180000ms exceeded.
Call log:
- waiting for locator('[data-testid="critical-css-meta"]').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.waitForCriticalCssMetaInfoVisibility (/home/runner/work/jetpack/jetpack/projects/plugins/boost/tests/e2e/lib/pages/wp-admin/JetpackBoostPage.js:106:15)
at /home/runner/work/jetpack/jetpack/projects/plugins/boost/tests/e2e/specs/critical-css/critical-css.test.js:65:27
|
|
Run Jetpack Boost - Critical CSS tests:
tools/e2e-commons/pages/page-actions.js#L320
2) [chromium] › 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 #2 ───────────────────────────────────────────────────────────────────────────────────────
TimeoutError: locator.waitFor: Timeout 180000ms exceeded.
Call log:
- waiting for locator('[data-testid="critical-css-meta"]').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.waitForCriticalCssMetaInfoVisibility (/home/runner/work/jetpack/jetpack/projects/plugins/boost/tests/e2e/lib/pages/wp-admin/JetpackBoostPage.js:106:15)
at /home/runner/work/jetpack/jetpack/projects/plugins/boost/tests/e2e/specs/critical-css/critical-css.test.js:65:27
|
|
Run Jetpack Boost - Critical CSS tests:
projects/plugins/boost/tests/e2e/specs/critical-css/critical-css.test.js#L72
3) [chromium] › 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
|
|
Run Jetpack Boost - Critical CSS tests:
projects/plugins/boost/tests/e2e/specs/critical-css/critical-css.test.js#L72
3) [chromium] › 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
|
|
Run Jetpack Boost - Critical CSS tests:
projects/plugins/boost/tests/e2e/specs/critical-css/critical-css.test.js#L72
3) [chromium] › 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 #2 ───────────────────────────────────────────────────────────────────────────────────────
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
|
|
Run Jetpack Boost - Critical CSS tests:
tools/e2e-commons/pages/page-actions.js#L320
4) [chromium] › 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('.jb-critical-css-progress').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.waitForCriticalCssGenerationProgressUIVisibility (/home/runner/work/jetpack/jetpack/projects/plugins/boost/tests/e2e/lib/pages/wp-admin/JetpackBoostPage.js:111:15)
at /home/runner/work/jetpack/jetpack/projects/plugins/boost/tests/e2e/specs/critical-css/critical-css.test.js:92:27
|
|
Run Jetpack Boost - Critical CSS tests
6 failed
[chromium] › specs/critical-css/critical-css.test.js:47:2 › Critical CSS module › Critical CSS should be generated when the module is active
[chromium] › 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
[chromium] › 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
[chromium] › specs/critical-css/critical-css.test.js:76:2 › Critical CSS module › Critical CSS Admin message should show when the theme is changed
[chromium] › specs/critical-css/critical-css.test.js:101:2 › Critical CSS module › Critical CSS should be generated with an error (advanced recommendations)
[chromium] › 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
2 passed (18.7m)
|
Loading