Boost: Add foundation pages support #91849
e2e-tests.yml
on: pull_request
Annotations
7 errors and 7 notices
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/modules/speed-score.test.js:33:2 › Speed Score feature › The Speed Scores should be able to refresh:
projects/plugins/boost/tests/e2e/specs/modules/speed-score.test.js#L37
1) specs/modules/speed-score.test.js:33:2 › Speed Score feature › The Speed Scores should be able to refresh
Error: Score should be loading
expect(received).toBeTruthy()
Received: null
35 | await jetpackBoostPage.clickRefreshSpeedScore();
36 |
> 37 | expect( await jetpackBoostPage.isScoreLoading(), 'Score should be loading' ).toBeTruthy();
| ^
38 | await jetpackBoostPage.waitForScoreLoadingToFinish();
39 | expect( await jetpackBoostPage.isScoreVisible(), 'Score should be displayed' ).toBeTruthy();
40 | } );
at /home/runner/work/jetpack/jetpack/projects/plugins/boost/tests/e2e/specs/modules/speed-score.test.js:37:80
|
specs/modules/speed-score.test.js:33:2 › Speed Score feature › The Speed Scores should be able to refresh:
projects/plugins/boost/tests/e2e/specs/modules/speed-score.test.js#L39
1) specs/modules/speed-score.test.js:33:2 › Speed Score feature › The Speed Scores should be able to refresh
Retry #1 ───────────────────────────────────────────────────────────────────────────────────────
Error: Score should be displayed
expect(received).toBeTruthy()
Received: null
37 | expect( await jetpackBoostPage.isScoreLoading(), 'Score should be loading' ).toBeTruthy();
38 | await jetpackBoostPage.waitForScoreLoadingToFinish();
> 39 | expect( await jetpackBoostPage.isScoreVisible(), 'Score should be displayed' ).toBeTruthy();
| ^
40 | } );
41 |
42 | test( 'Should be able to click info icon next to overall score and see the detailed overall score description popin', async () => {
at /home/runner/work/jetpack/jetpack/projects/plugins/boost/tests/e2e/specs/modules/speed-score.test.js:39:82
|
Jetpack Boost - Modules e2e tests
Process completed with exit code 1.
|
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
1) 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
1) 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
|
Jetpack Boost - Critical CSS e2e tests
Process completed with exit code 1.
|
🎭 Playwright Run Summary
4 passed (53.3s)
|
🎭 Playwright Run Summary
2 passed (49.4s)
|
🎭 Playwright Run Summary
5 passed (1.3m)
|
🎭 Playwright Run Summary
5 passed (1.2m)
|
🎭 Playwright Run Summary
1 failed
specs/modules/speed-score.test.js:33:2 › Speed Score feature › The Speed Scores should be able to refresh
12 passed (1.9m)
|
🎭 Playwright Run Summary
6 passed (2.1m)
|
🎭 Playwright Run Summary
1 failed
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
7 passed (2.5m)
|
Artifacts
Produced during runtime
Name | Size | |
---|---|---|
test-output-Jetpack Boost - Base
|
15.3 KB |
|
test-output-Jetpack Boost - Critical CSS
|
4.54 MB |
|
test-output-Jetpack Boost - Image CDN
|
9.56 KB |
|
test-output-Jetpack Boost - Image Guide
|
7.46 KB |
|
test-output-Jetpack Boost - Modules
|
3.14 MB |
|
test-output-Jetpack Boost - Page Cache
|
12.4 KB |
|