Stabilize toolbar E2E with local fixture server #55
Annotations
10 errors, 1 warning, and 1 notice
|
[chromium] › e2e/tests/extension.spec.ts:18:2 › Per-domain activation › when domain is enabled in storage:
e2e/fixtures.ts#L41
2) [chromium] › e2e/tests/extension.spec.ts:18:2 › Per-domain activation › when domain is enabled in storage, inspector is active on page load
Retry #1 ───────────────────────────────────────────────────────────────────────────────────────
Error: browserContext.waitForEvent: Target page, context or browser has been closed
at fixtures.ts:41
39 | let [background] = context.serviceWorkers();
40 | if (!background) {
> 41 | background = await context.waitForEvent("serviceworker");
| ^
42 | }
43 | const extensionId = background.url().split("/")[2];
44 | await use(extensionId);
at Object.extensionId (/home/runner/work/amgiflol/amgiflol/e2e/fixtures.ts:41:31)
|
|
[chromium] › e2e/tests/extension.spec.ts:18:2 › Per-domain activation › when domain is enabled in storage:
e2e/tests/extension.spec.ts#L0
2) [chromium] › e2e/tests/extension.spec.ts:18:2 › Per-domain activation › when domain is enabled in storage, inspector is active on page load
Retry #1 ───────────────────────────────────────────────────────────────────────────────────────
Test timeout of 5000ms exceeded while setting up "extensionId".
|
|
[chromium] › e2e/tests/extension.spec.ts:18:2 › Per-domain activation › when domain is enabled in storage:
e2e/fixtures.ts#L41
2) [chromium] › e2e/tests/extension.spec.ts:18:2 › Per-domain activation › when domain is enabled in storage, inspector is active on page load
Error: browserContext.waitForEvent: Target page, context or browser has been closed
at fixtures.ts:41
39 | let [background] = context.serviceWorkers();
40 | if (!background) {
> 41 | background = await context.waitForEvent("serviceworker");
| ^
42 | }
43 | const extensionId = background.url().split("/")[2];
44 | await use(extensionId);
at Object.extensionId (/home/runner/work/amgiflol/amgiflol/e2e/fixtures.ts:41:31)
|
|
[chromium] › e2e/tests/extension.spec.ts:18:2 › Per-domain activation › when domain is enabled in storage:
e2e/tests/extension.spec.ts#L0
2) [chromium] › e2e/tests/extension.spec.ts:18:2 › Per-domain activation › when domain is enabled in storage, inspector is active on page load
Test timeout of 5000ms exceeded while setting up "extensionId".
|
|
[chromium] › e2e/tests/extension.spec.ts:11:2 › Content injection › inspector root and app load on supported page:
e2e/tests/extension.spec.ts#L13
1) [chromium] › e2e/tests/extension.spec.ts:11:2 › Content injection › inspector root and app load on supported page
Retry #2 ───────────────────────────────────────────────────────────────────────────────────────
Error: expect(locator).toHaveCount(expected) failed
Locator: locator('[data-amgiflol-root]')
Expected: 1
Received: 0
Call log:
- Expect "toHaveCount" with timeout 5000ms
- waiting for locator('[data-amgiflol-root]')
8 × locator resolved to 0 elements
- unexpected value "0"
11 | test("inspector root and app load on supported page", async ({ page }) => {
12 | await openStableTestPage(page);
> 13 | await expect(getExtensionRoot(page)).toHaveCount(1);
| ^
14 | });
15 | });
16 |
at /home/runner/work/amgiflol/amgiflol/e2e/tests/extension.spec.ts:13:40
|
|
[chromium] › e2e/tests/extension.spec.ts:11:2 › Content injection › inspector root and app load on supported page:
e2e/tests/extension.spec.ts#L0
1) [chromium] › e2e/tests/extension.spec.ts:11:2 › Content injection › inspector root and app load on supported page
Retry #2 ───────────────────────────────────────────────────────────────────────────────────────
Test timeout of 5000ms exceeded.
|
|
[chromium] › e2e/tests/extension.spec.ts:11:2 › Content injection › inspector root and app load on supported page:
e2e/tests/extension.spec.ts#L13
1) [chromium] › e2e/tests/extension.spec.ts:11:2 › Content injection › inspector root and app load on supported page
Retry #1 ───────────────────────────────────────────────────────────────────────────────────────
Error: expect(locator).toHaveCount(expected) failed
Locator: locator('[data-amgiflol-root]')
Expected: 1
Received: 0
Call log:
- Expect "toHaveCount" with timeout 5000ms
- waiting for locator('[data-amgiflol-root]')
7 × locator resolved to 0 elements
- unexpected value "0"
11 | test("inspector root and app load on supported page", async ({ page }) => {
12 | await openStableTestPage(page);
> 13 | await expect(getExtensionRoot(page)).toHaveCount(1);
| ^
14 | });
15 | });
16 |
at /home/runner/work/amgiflol/amgiflol/e2e/tests/extension.spec.ts:13:40
|
|
[chromium] › e2e/tests/extension.spec.ts:11:2 › Content injection › inspector root and app load on supported page:
e2e/tests/extension.spec.ts#L0
1) [chromium] › e2e/tests/extension.spec.ts:11:2 › Content injection › inspector root and app load on supported page
Retry #1 ───────────────────────────────────────────────────────────────────────────────────────
Test timeout of 5000ms exceeded.
|
|
[chromium] › e2e/tests/extension.spec.ts:11:2 › Content injection › inspector root and app load on supported page:
e2e/tests/extension.spec.ts#L13
1) [chromium] › e2e/tests/extension.spec.ts:11:2 › Content injection › inspector root and app load on supported page
Error: expect(locator).toHaveCount(expected) failed
Locator: locator('[data-amgiflol-root]')
Expected: 1
Received: 0
Call log:
- Expect "toHaveCount" with timeout 5000ms
- waiting for locator('[data-amgiflol-root]')
7 × locator resolved to 0 elements
- unexpected value "0"
11 | test("inspector root and app load on supported page", async ({ page }) => {
12 | await openStableTestPage(page);
> 13 | await expect(getExtensionRoot(page)).toHaveCount(1);
| ^
14 | });
15 | });
16 |
at /home/runner/work/amgiflol/amgiflol/e2e/tests/extension.spec.ts:13:40
|
|
[chromium] › e2e/tests/extension.spec.ts:11:2 › Content injection › inspector root and app load on supported page:
e2e/tests/extension.spec.ts#L0
1) [chromium] › e2e/tests/extension.spec.ts:11:2 › Content injection › inspector root and app load on supported page
Test timeout of 5000ms exceeded.
|
|
test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
🎭 Playwright Run Summary
8 failed
[chromium] › e2e/tests/extension.spec.ts:11:2 › Content injection › inspector root and app load on supported page
[chromium] › e2e/tests/extension.spec.ts:18:2 › Per-domain activation › when domain is enabled in storage, inspector is active on page load
[chromium] › e2e/tests/popup.spec.ts:5:2 › Popup › popup shows correct UI and updates storage when toggled
[chromium] › e2e/tests/sidepanel.spec.ts:11:2 › Side panel › side panel can be shown from toolbar
[chromium] › e2e/tests/toolbar-distances.spec.ts:11:2 › Toolbar distances › distance lines appear after hover when enabled
[chromium] › e2e/tests/toolbar-overlays.spec.ts:11:2 › Toolbar overlays › grid overlay can be toggled
[chromium] › e2e/tests/toolbar-overlays.spec.ts:26:2 › Toolbar overlays › ruler overlay can be toggled
[chromium] › e2e/tests/toolbar-settings.spec.ts:11:2 › Toolbar settings menu › feature voting and behaviour toggles are visible and interactive
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
playwright-report
Expired
|
1.23 MB |
sha256:6c6b8c02713c2437196ae027726e9c9edcfd0c26f29dc62a8e2cdd6fe93e3f8f
|
|