Detail view responsive improvements (2483) by @laurakwhit (Attempt 1) #4101
laurakwhitplaywright.yml
on: pull_request
integration-tests
7m 29s
e2e-tests
4m 40s
Annotations
10 errors, 3 warnings, and 2 notices
|
[chromium desktop] › integration/disable-write-actions.spec.ts:16:3 › Enable write actions by default › Cancel workflow button enabled:
tests/integration/disable-write-actions.spec.ts#L20
1) [chromium desktop] › integration/disable-write-actions.spec.ts:16:3 › Enable write actions by default › Cancel workflow button enabled
Error: expect.toBeEnabled: Error: strict mode violation: locator('#workflow-actions-primary-button') resolved to 2 elements:
1) <button type="button" id="workflow-actions-primary-butto…> Request Cancellation </button> aka getByText('Request Cancellation').first()
2) <button type="button" id="workflow-actions-primary-butto…> Request Cancellation </button> aka getByRole('button', { name: 'Request Cancellation' })
Call log:
- expect.toBeEnabled with timeout 10000ms
- waiting for locator('#workflow-actions-primary-button')
18 | '#workflow-actions-primary-button',
19 | );
> 20 | await expect(workflowActionButton).toBeEnabled();
| ^
21 | });
22 | });
23 |
at /home/runner/work/ui/ui/tests/integration/disable-write-actions.spec.ts:20:40
|
|
[chromium desktop] › integration/disable-write-actions.spec.ts:16:3 › Enable write actions by default › Cancel workflow button enabled:
tests/integration/disable-write-actions.spec.ts#L20
1) [chromium desktop] › integration/disable-write-actions.spec.ts:16:3 › Enable write actions by default › Cancel workflow button enabled
Retry #1 ───────────────────────────────────────────────────────────────────────────────────────
Error: expect.toBeEnabled: Error: strict mode violation: locator('#workflow-actions-primary-button') resolved to 2 elements:
1) <button type="button" id="workflow-actions-primary-butto…> Request Cancellation </button> aka getByText('Request Cancellation').first()
2) <button type="button" id="workflow-actions-primary-butto…> Request Cancellation </button> aka getByRole('button', { name: 'Request Cancellation' })
Call log:
- expect.toBeEnabled with timeout 10000ms
- waiting for locator('#workflow-actions-primary-button')
18 | '#workflow-actions-primary-button',
19 | );
> 20 | await expect(workflowActionButton).toBeEnabled();
| ^
21 | });
22 | });
23 |
at /home/runner/work/ui/ui/tests/integration/disable-write-actions.spec.ts:20:40
|
|
[chromium desktop] › integration/disable-write-actions.spec.ts:16:3 › Enable write actions by default › Cancel workflow button enabled:
tests/integration/disable-write-actions.spec.ts#L20
1) [chromium desktop] › integration/disable-write-actions.spec.ts:16:3 › Enable write actions by default › Cancel workflow button enabled
Retry #2 ───────────────────────────────────────────────────────────────────────────────────────
Error: expect.toBeEnabled: Error: strict mode violation: locator('#workflow-actions-primary-button') resolved to 2 elements:
1) <button type="button" id="workflow-actions-primary-butto…> Request Cancellation </button> aka getByText('Request Cancellation').first()
2) <button type="button" id="workflow-actions-primary-butto…> Request Cancellation </button> aka getByRole('button', { name: 'Request Cancellation' })
Call log:
- expect.toBeEnabled with timeout 10000ms
- waiting for locator('#workflow-actions-primary-button')
18 | '#workflow-actions-primary-button',
19 | );
> 20 | await expect(workflowActionButton).toBeEnabled();
| ^
21 | });
22 | });
23 |
at /home/runner/work/ui/ui/tests/integration/disable-write-actions.spec.ts:20:40
|
|
[chromium desktop] › integration/disable-write-actions.spec.ts:16:3 › Enable write actions by default › Cancel workflow button enabled:
tests/integration/disable-write-actions.spec.ts#L20
1) [chromium desktop] › integration/disable-write-actions.spec.ts:16:3 › Enable write actions by default › Cancel workflow button enabled
Retry #3 ───────────────────────────────────────────────────────────────────────────────────────
Error: expect.toBeEnabled: Error: strict mode violation: locator('#workflow-actions-primary-button') resolved to 2 elements:
1) <button type="button" id="workflow-actions-primary-butto…> Request Cancellation </button> aka getByText('Request Cancellation').first()
2) <button type="button" id="workflow-actions-primary-butto…> Request Cancellation </button> aka getByRole('button', { name: 'Request Cancellation' })
Call log:
- expect.toBeEnabled with timeout 10000ms
- waiting for locator('#workflow-actions-primary-button')
18 | '#workflow-actions-primary-button',
19 | );
> 20 | await expect(workflowActionButton).toBeEnabled();
| ^
21 | });
22 | });
23 |
at /home/runner/work/ui/ui/tests/integration/disable-write-actions.spec.ts:20:40
|
|
[chromium desktop] › integration/disable-write-actions.spec.ts:31:3 › Disable write actions on workflow actions › Cancel workflow button disabled:
tests/integration/disable-write-actions.spec.ts#L35
2) [chromium desktop] › integration/disable-write-actions.spec.ts:31:3 › Disable write actions on workflow actions › Cancel workflow button disabled
Error: expect.toBeDisabled: Error: strict mode violation: locator('#workflow-actions-primary-button') resolved to 2 elements:
1) <button disabled type="button" id="workflow-actions-prim…> Request Cancellation </button> aka getByText('Request Cancellation').first()
2) <button disabled type="button" id="workflow-actions-prim…> Request Cancellation </button> aka getByRole('button', { name: 'Request Cancellation' })
Call log:
- expect.toBeDisabled with timeout 10000ms
- waiting for locator('#workflow-actions-primary-button')
33 | '#workflow-actions-primary-button',
34 | );
> 35 | await expect(workflowActionButton).toBeDisabled();
| ^
36 | });
37 | });
38 |
at /home/runner/work/ui/ui/tests/integration/disable-write-actions.spec.ts:35:40
|
|
[chromium desktop] › integration/disable-write-actions.spec.ts:31:3 › Disable write actions on workflow actions › Cancel workflow button disabled:
tests/integration/disable-write-actions.spec.ts#L35
2) [chromium desktop] › integration/disable-write-actions.spec.ts:31:3 › Disable write actions on workflow actions › Cancel workflow button disabled
Retry #1 ───────────────────────────────────────────────────────────────────────────────────────
Error: expect.toBeDisabled: Error: strict mode violation: locator('#workflow-actions-primary-button') resolved to 2 elements:
1) <button disabled type="button" id="workflow-actions-prim…> Request Cancellation </button> aka getByText('Request Cancellation').first()
2) <button disabled type="button" id="workflow-actions-prim…> Request Cancellation </button> aka getByRole('button', { name: 'Request Cancellation' })
Call log:
- expect.toBeDisabled with timeout 10000ms
- waiting for locator('#workflow-actions-primary-button')
33 | '#workflow-actions-primary-button',
34 | );
> 35 | await expect(workflowActionButton).toBeDisabled();
| ^
36 | });
37 | });
38 |
at /home/runner/work/ui/ui/tests/integration/disable-write-actions.spec.ts:35:40
|
|
[chromium desktop] › integration/disable-write-actions.spec.ts:31:3 › Disable write actions on workflow actions › Cancel workflow button disabled:
tests/integration/disable-write-actions.spec.ts#L35
2) [chromium desktop] › integration/disable-write-actions.spec.ts:31:3 › Disable write actions on workflow actions › Cancel workflow button disabled
Retry #2 ───────────────────────────────────────────────────────────────────────────────────────
Error: expect.toBeDisabled: Error: strict mode violation: locator('#workflow-actions-primary-button') resolved to 2 elements:
1) <button disabled type="button" id="workflow-actions-prim…> Request Cancellation </button> aka getByText('Request Cancellation').first()
2) <button disabled type="button" id="workflow-actions-prim…> Request Cancellation </button> aka getByRole('button', { name: 'Request Cancellation' })
Call log:
- expect.toBeDisabled with timeout 10000ms
- waiting for locator('#workflow-actions-primary-button')
33 | '#workflow-actions-primary-button',
34 | );
> 35 | await expect(workflowActionButton).toBeDisabled();
| ^
36 | });
37 | });
38 |
at /home/runner/work/ui/ui/tests/integration/disable-write-actions.spec.ts:35:40
|
|
[chromium desktop] › integration/disable-write-actions.spec.ts:31:3 › Disable write actions on workflow actions › Cancel workflow button disabled:
tests/integration/disable-write-actions.spec.ts#L35
2) [chromium desktop] › integration/disable-write-actions.spec.ts:31:3 › Disable write actions on workflow actions › Cancel workflow button disabled
Retry #3 ───────────────────────────────────────────────────────────────────────────────────────
Error: expect.toBeDisabled: Error: strict mode violation: locator('#workflow-actions-primary-button') resolved to 2 elements:
1) <button disabled type="button" id="workflow-actions-prim…> Request Cancellation </button> aka getByText('Request Cancellation').first()
2) <button disabled type="button" id="workflow-actions-prim…> Request Cancellation </button> aka getByRole('button', { name: 'Request Cancellation' })
Call log:
- expect.toBeDisabled with timeout 10000ms
- waiting for locator('#workflow-actions-primary-button')
33 | '#workflow-actions-primary-button',
34 | );
> 35 | await expect(workflowActionButton).toBeDisabled();
| ^
36 | });
37 | });
38 |
at /home/runner/work/ui/ui/tests/integration/disable-write-actions.spec.ts:35:40
|
|
[chromium desktop] › integration/workflow-actions.spec.ts:33:5 › Workflow Actions for a Completed Workflow › Workflow Reset for server version <1.24 › is disabled when global write actions are disabled via Settings API:
tests/integration/workflow-actions.spec.ts#L38
3) [chromium desktop] › integration/workflow-actions.spec.ts:33:5 › Workflow Actions for a Completed Workflow › Workflow Reset for server version <1.24 › is disabled when global write actions are disabled via Settings API
Error: expect.toBeDisabled: Error: strict mode violation: getByTestId('workflow-reset-button') resolved to 2 elements:
1) <button disabled type="button" aria-label="Reset" data-t…> Reset </button> aka getByTestId('workflow-reset-button').first()
2) <button disabled type="button" aria-label="Reset" data-t…> Reset </button> aka getByRole('button', { name: 'Reset' })
Call log:
- expect.toBeDisabled with timeout 10000ms
- waiting for getByTestId('workflow-reset-button')
36 | await mockSettingsApi(page, { DisableWriteActions: true });
37 |
> 38 | await expect(page.getByTestId('workflow-reset-button')).toBeDisabled();
| ^
39 | });
40 |
41 | test('is disabled when reset is disabled via Settings API', async ({
at /home/runner/work/ui/ui/tests/integration/workflow-actions.spec.ts:38:63
|
|
[chromium desktop] › integration/workflow-actions.spec.ts:33:5 › Workflow Actions for a Completed Workflow › Workflow Reset for server version <1.24 › is disabled when global write actions are disabled via Settings API:
tests/integration/workflow-actions.spec.ts#L38
3) [chromium desktop] › integration/workflow-actions.spec.ts:33:5 › Workflow Actions for a Completed Workflow › Workflow Reset for server version <1.24 › is disabled when global write actions are disabled via Settings API
Retry #1 ───────────────────────────────────────────────────────────────────────────────────────
Error: expect.toBeDisabled: Error: strict mode violation: getByTestId('workflow-reset-button') resolved to 2 elements:
1) <button disabled type="button" aria-label="Reset" data-t…> Reset </button> aka getByTestId('workflow-reset-button').first()
2) <button disabled type="button" aria-label="Reset" data-t…> Reset </button> aka getByRole('button', { name: 'Reset' })
Call log:
- expect.toBeDisabled with timeout 10000ms
- waiting for getByTestId('workflow-reset-button')
36 | await mockSettingsApi(page, { DisableWriteActions: true });
37 |
> 38 | await expect(page.getByTestId('workflow-reset-button')).toBeDisabled();
| ^
39 | });
40 |
41 | test('is disabled when reset is disabled via Settings API', async ({
at /home/runner/work/ui/ui/tests/integration/workflow-actions.spec.ts:38:63
|
|
e2e-tests
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
integration-tests
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Deprecation notice: v1, v2, and v3 of the artifact actions
The following artifacts were uploaded using a version of actions/upload-artifact that is scheduled for deprecation: "playwright-report-e2e", "playwright-report-integration".
Please update your workflow to use v4 of the artifact actions.
Learn more: https://github.blog/changelog/2024-04-16-deprecation-notice-v3-of-the-artifact-actions/
|
|
🎭 Playwright Run Summary
5 skipped
15 passed (2.0m)
|
|
🎭 Playwright Run Summary
26 failed
[chromium desktop] › integration/disable-write-actions.spec.ts:16:3 › Enable write actions by default › Cancel workflow button enabled
[chromium desktop] › integration/disable-write-actions.spec.ts:31:3 › Disable write actions on workflow actions › Cancel workflow button disabled
[chromium desktop] › integration/workflow-actions.spec.ts:33:5 › Workflow Actions for a Completed Workflow › Workflow Reset for server version <1.24 › is disabled when global write actions are disabled via Settings API
[chromium desktop] › integration/workflow-actions.spec.ts:41:5 › Workflow Actions for a Completed Workflow › Workflow Reset for server version <1.24 › is disabled when reset is disabled via Settings API
[chromium desktop] › integration/workflow-actions.spec.ts:49:5 › Workflow Actions for a Completed Workflow › Workflow Reset for server version <1.24 › allows reapplying signals after the reset point
[chromium desktop] › integration/workflow-actions.spec.ts:75:5 › Workflow Actions for a Completed Workflow › Workflow Reset for server version <1.24 › allows NOT reapplying signals after the reset point
[chromium desktop] › integration/workflow-actions.spec.ts:113:5 › Workflow Actions for a Completed Workflow › Workflow Reset for server version >=1.24 › Allows reapplying Signals and Updates after the reset point
[chromium desktop] › integration/workflow-actions.spec.ts:141:5 › Workflow Actions for a Completed Workflow › Workflow Reset for server version >=1.24 › Allows excluding Signals after the reset point
[chromium desktop] › integration/workflow-actions.spec.ts:169:5 › Workflow Actions for a Completed Workflow › Workflow Reset for server version >=1.24 › Allows excluding Updates after the reset point
[chromium desktop] › integration/workflow-actions.spec.ts:214:3 › Workflow actions for a Running Workflow › All actions are disabled when global write actions are disabled via Settings API
[chromium desktop] › integration/workflow-actions.spec.ts:227:5 › Workflow actions for a Running Workflow › Workflow Cancel › is disabled when cancel is disabled via Settings API
[chromium desktop] › integration/workflow-actions.spec.ts:253:5 › Workflow actions for a Running Workflow › Workflow Terminate › is disabled when teminate is disabled via Settings API
[chromium desktop] › integration/workflow-actions.spec.ts:279:5 › Workflow actions for a Running Workflow › Workflow Signal › is disabled when signal is disabled via Settings API
[chromium mobile] › integration/disable-write-actions.spec.ts:16:3 › Enable write actions by default › Cancel workflow button enabled
[chromium mobile] › integration/disable-write-actions.spec.ts:31:3 › Disable write actions on workflow actions › Cancel workflow button disabled
[chromium mobile] › integration/workflow-actions.spec.ts:33:5 › Workflow Actions for a Completed Workflow › Workflow Reset for server version <1.24 › is disabled when global write actions are disabled via Settings API
[chromium mobile] › integration/workflow-actions.spec.ts:41:5 › Workflow Actions for a Completed Workflow › Workflow Reset for server version <1.24 › is disabled when reset is disabled via Settings API
[chromium mobile] › integration/workflow-actions.spec.ts:49:5 › Workflow Actions for a Completed Workflow › Workflow Reset for server version <1.24 › allows reapplying signals after the reset point
[chromium mobile] › integration/workflow-actions.spec.ts:75:5 › Workflow Actions for a Completed Workflow › Workflow Reset for server version <1.24 › allows NOT reapplying signals after the reset point
[chromium mobile] › integration/workflow-actions.spec.ts:113:5 › Workflow Actions for a Completed Workflow › Workflow Reset for server version >=1.24 › Allows reapplying Signals and Updates after the reset point
[chromium mobile] › integration/workflow-actions.spec.ts:141:5 › Workflow Actions for a Completed Workflow › Workflow Reset for server version >=1.24 › Allows excluding Signals after the reset point
[chromium mobile
|
Artifacts
Produced during runtime
| Name | Size | |
|---|---|---|
|
playwright-report-e2e
|
461 KB |
|
|
playwright-report-integration
|
84.9 MB |
|