Photon: update filter docblock to match possible types #77165
jehervee2e-tests.yml
on: pull_request
Annotations
10 errors and 7 notices
|
specs/critical-css/critical-css.test.js:27:2 › Critical CSS module › No Critical CSS meta information should show on the admin when the module is inactive:
tools/e2e-commons/pages/page-actions.js#L314
1) specs/critical-css/critical-css.test.js:27:2 › Critical CSS module › No Critical CSS meta information should show on the admin when the module is inactive
TimeoutError: page.waitForSelector: Timeout 20000ms exceeded.
=========================== logs ===========================
waiting for locator('#jb-dashboard') to be visible
============================================================
at ../../../../../tools/e2e-commons/pages/page-actions.js:314
312 | `Waiting for element '${ selector }' to be ${ state } [timeout: ${ timeout } ms]`
313 | );
> 314 | return await this.page.waitForSelector( selector, { state, timeout } );
| ^
315 | }
316 |
317 | /**
at JetpackBoostPage.waitForElementState (/home/runner/work/jetpack/jetpack/tools/e2e-commons/pages/page-actions.js:314:26)
at JetpackBoostPage.waitForElementToBeVisible (/home/runner/work/jetpack/jetpack/tools/e2e-commons/pages/page-actions.js:264:21)
at JetpackBoostPage.waitForPage (/home/runner/work/jetpack/jetpack/tools/e2e-commons/pages/page-actions.js:63: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:29:28
|
|
specs/critical-css/critical-css.test.js:27:2 › Critical CSS module › No Critical CSS meta information should show on the admin when the module is inactive:
tools/e2e-commons/pages/page-actions.js#L314
1) specs/critical-css/critical-css.test.js:27:2 › Critical CSS module › No Critical CSS meta information should show on the admin when the module is inactive
Retry #1 ───────────────────────────────────────────────────────────────────────────────────────
TimeoutError: page.waitForSelector: Timeout 20000ms exceeded.
=========================== logs ===========================
waiting for locator('#jb-dashboard') to be visible
============================================================
at ../../../../../tools/e2e-commons/pages/page-actions.js:314
312 | `Waiting for element '${ selector }' to be ${ state } [timeout: ${ timeout } ms]`
313 | );
> 314 | return await this.page.waitForSelector( selector, { state, timeout } );
| ^
315 | }
316 |
317 | /**
at JetpackBoostPage.waitForElementState (/home/runner/work/jetpack/jetpack/tools/e2e-commons/pages/page-actions.js:314:26)
at JetpackBoostPage.waitForElementToBeVisible (/home/runner/work/jetpack/jetpack/tools/e2e-commons/pages/page-actions.js:264:21)
at JetpackBoostPage.waitForPage (/home/runner/work/jetpack/jetpack/tools/e2e-commons/pages/page-actions.js:63: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:29:28
|
|
specs/critical-css/critical-css.test.js:47:2 › Critical CSS module › Critical CSS should be generated when the module is active:
tools/e2e-commons/pages/page-actions.js#L314
2) specs/critical-css/critical-css.test.js:47:2 › Critical CSS module › Critical CSS should be generated when the module is active
TimeoutError: page.waitForSelector: Timeout 20000ms exceeded.
=========================== logs ===========================
waiting for locator('#jb-dashboard') to be visible
============================================================
at ../../../../../tools/e2e-commons/pages/page-actions.js:314
312 | `Waiting for element '${ selector }' to be ${ state } [timeout: ${ timeout } ms]`
313 | );
> 314 | return await this.page.waitForSelector( selector, { state, timeout } );
| ^
315 | }
316 |
317 | /**
at JetpackBoostPage.waitForElementState (/home/runner/work/jetpack/jetpack/tools/e2e-commons/pages/page-actions.js:314:26)
at JetpackBoostPage.waitForElementToBeVisible (/home/runner/work/jetpack/jetpack/tools/e2e-commons/pages/page-actions.js:264:21)
at JetpackBoostPage.waitForPage (/home/runner/work/jetpack/jetpack/tools/e2e-commons/pages/page-actions.js:63: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:49:28
|
|
specs/critical-css/critical-css.test.js:47:2 › Critical CSS module › Critical CSS should be generated when the module is active:
tools/e2e-commons/pages/page-actions.js#L314
2) 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: page.waitForSelector: Timeout 20000ms exceeded.
=========================== logs ===========================
waiting for locator('#jb-dashboard') to be visible
============================================================
at ../../../../../tools/e2e-commons/pages/page-actions.js:314
312 | `Waiting for element '${ selector }' to be ${ state } [timeout: ${ timeout } ms]`
313 | );
> 314 | return await this.page.waitForSelector( selector, { state, timeout } );
| ^
315 | }
316 |
317 | /**
at JetpackBoostPage.waitForElementState (/home/runner/work/jetpack/jetpack/tools/e2e-commons/pages/page-actions.js:314:26)
at JetpackBoostPage.waitForElementToBeVisible (/home/runner/work/jetpack/jetpack/tools/e2e-commons/pages/page-actions.js:264:21)
at JetpackBoostPage.waitForPage (/home/runner/work/jetpack/jetpack/tools/e2e-commons/pages/page-actions.js:63: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:49: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#L314
3) 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: page.waitForSelector: Timeout 20000ms exceeded.
=========================== logs ===========================
waiting for locator('#jb-dashboard') to be visible
============================================================
at ../../../../../tools/e2e-commons/pages/page-actions.js:314
312 | `Waiting for element '${ selector }' to be ${ state } [timeout: ${ timeout } ms]`
313 | );
> 314 | return await this.page.waitForSelector( selector, { state, timeout } );
| ^
315 | }
316 |
317 | /**
at JetpackBoostPage.waitForElementState (/home/runner/work/jetpack/jetpack/tools/e2e-commons/pages/page-actions.js:314:26)
at JetpackBoostPage.waitForElementToBeVisible (/home/runner/work/jetpack/jetpack/tools/e2e-commons/pages/page-actions.js:264:21)
at JetpackBoostPage.waitForPage (/home/runner/work/jetpack/jetpack/tools/e2e-commons/pages/page-actions.js:63: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: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#L314
3) 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: page.waitForSelector: Timeout 20000ms exceeded.
=========================== logs ===========================
waiting for locator('#jb-dashboard') to be visible
============================================================
at ../../../../../tools/e2e-commons/pages/page-actions.js:314
312 | `Waiting for element '${ selector }' to be ${ state } [timeout: ${ timeout } ms]`
313 | );
> 314 | return await this.page.waitForSelector( selector, { state, timeout } );
| ^
315 | }
316 |
317 | /**
at JetpackBoostPage.waitForElementState (/home/runner/work/jetpack/jetpack/tools/e2e-commons/pages/page-actions.js:314:26)
at JetpackBoostPage.waitForElementToBeVisible (/home/runner/work/jetpack/jetpack/tools/e2e-commons/pages/page-actions.js:264:21)
at JetpackBoostPage.waitForPage (/home/runner/work/jetpack/jetpack/tools/e2e-commons/pages/page-actions.js:63: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
4) 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.
=========================== logs ===========================
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
4) 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.
=========================== logs ===========================
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#L314
5) specs/critical-css/critical-css.test.js:76:2 › Critical CSS module › Critical CSS Admin message should show when the theme is changed
TimeoutError: page.waitForSelector: Timeout 20000ms exceeded.
=========================== logs ===========================
waiting for locator('#dashboard-widgets-wrap') to be visible
============================================================
at ../../../../../tools/e2e-commons/pages/page-actions.js:314
312 | `Waiting for element '${ selector }' to be ${ state } [timeout: ${ timeout } ms]`
313 | );
> 314 | return await this.page.waitForSelector( selector, { state, timeout } );
| ^
315 | }
316 |
317 | /**
at DashboardPage.waitForElementState (/home/runner/work/jetpack/jetpack/tools/e2e-commons/pages/page-actions.js:314:26)
at DashboardPage.waitForElementToBeVisible (/home/runner/work/jetpack/jetpack/tools/e2e-commons/pages/page-actions.js:264:21)
at DashboardPage.waitForPage (/home/runner/work/jetpack/jetpack/tools/e2e-commons/pages/page-actions.js:63: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#L314
5) 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: page.waitForSelector: Timeout 20000ms exceeded.
=========================== logs ===========================
waiting for locator('#dashboard-widgets-wrap') to be visible
============================================================
at ../../../../../tools/e2e-commons/pages/page-actions.js:314
312 | `Waiting for element '${ selector }' to be ${ state } [timeout: ${ timeout } ms]`
313 | );
> 314 | return await this.page.waitForSelector( selector, { state, timeout } );
| ^
315 | }
316 |
317 | /**
at DashboardPage.waitForElementState (/home/runner/work/jetpack/jetpack/tools/e2e-commons/pages/page-actions.js:314:26)
at DashboardPage.waitForElementToBeVisible (/home/runner/work/jetpack/jetpack/tools/e2e-commons/pages/page-actions.js:264:21)
at DashboardPage.waitForPage (/home/runner/work/jetpack/jetpack/tools/e2e-commons/pages/page-actions.js:63: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
|
|
🎭 Playwright Run Summary
2 passed (1.1m)
|
|
🎭 Playwright Run Summary
1 passed (1.1m)
|
|
🎭 Playwright Run Summary
13 passed (2.8m)
|
|
🎭 Playwright Run Summary
6 passed (2.9m)
|
|
🎭 Playwright Run Summary
2 passed (3.0m)
|
|
🎭 Playwright Run Summary
2 passed (3.6m)
|
|
🎭 Playwright Run Summary
7 failed
specs/critical-css/critical-css.test.js:27:2 › Critical CSS module › No Critical CSS meta information should show on the admin when the module is inactive
specs/critical-css/critical-css.test.js:47:2 › Critical CSS module › Critical CSS should be generated when the module is active
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
1 passed (8.7m)
|
Artifacts
Produced during runtime
| Name | Size | |
|---|---|---|
|
test-output-Jetpack Boost - Base
Expired
|
14.3 KB |
|
|
test-output-Jetpack Boost - Critical CSS
Expired
|
195 KB |
|
|
test-output-Jetpack Boost - Image Guide
Expired
|
10.6 KB |
|
|
test-output-Jetpack Boost - Modules
Expired
|
22.6 KB |
|
|
test-output-Jetpack connection
Expired
|
14.2 KB |
|
|
test-output-Jetpack post-connection
Expired
|
15 KB |
|
|
test-output-Jetpack pre-connection
Expired
|
6.54 KB |
|