Run test manually #281
run-test-manual.yml
on: workflow_dispatch
Annotations
3 errors, 9 warnings, and 9 notices
[e2e] › attributes.spec.ts:165:7 › TC: SALEOR_128 User should be able to edit existing e2e product attribute to be updated 1 attribute @e2e @attributes:
playwright/tests/attributes.spec.ts#L1
1) [e2e] › attributes.spec.ts:165:7 › TC: SALEOR_128 User should be able to edit existing e2e product attribute to be updated 1 attribute @e2e @attributes
Test timeout of 30000ms exceeded.
|
[e2e] › attributes.spec.ts:165:7 › TC: SALEOR_128 User should be able to edit existing e2e product attribute to be updated 1 attribute @e2e @attributes:
playwright/pages/attributesPage.ts#L93
1) [e2e] › attributes.spec.ts:165:7 › TC: SALEOR_128 User should be able to edit existing e2e product attribute to be updated 1 attribute @e2e @attributes
Error: locator.waitFor: Test timeout of 30000ms exceeded.
Call log:
- waiting for getByTestId('page-header').getByText('e2e product attribute to be updated 1') to be visible
at ../pages/attributesPage.ts:93
91 | await console.log(`Navigates to existing attribute page: ${existingAttributeUrl}`);
92 | await this.page.goto(existingAttributeUrl);
> 93 | await this.pageHeader.getByText(attributeName).waitFor({
| ^
94 | state: "visible",
95 | timeout: 30000,
96 | });
at AttributesPage.gotoExistingAttributePage (/home/runner/work/saleor-dashboard/saleor-dashboard/playwright/pages/attributesPage.ts:93:52)
at AttributesPage.waitForNetworkIdleAfterAction (/home/runner/work/saleor-dashboard/saleor-dashboard/playwright/pages/basePage.ts:127:5)
at /home/runner/work/saleor-dashboard/saleor-dashboard/playwright/tests/attributes.spec.ts:166:5
|
run-tests (1/2)
Process completed with exit code 1.
|
initialize-cloud
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-node@v3, actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
create-run-on-testmo
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-node@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
run-tests (2/2)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-node@v3, actions/upload-artifact@v3, actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
run-tests (1/2)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-node@v3, actions/upload-artifact@v3, actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
tests-complete
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-node@v3, actions/download-artifact@v3, actions/upload-artifact@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
tests-complete
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
tests-complete
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
tests-complete
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
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: "all-blob-reports", "html-report--attempt-1".
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/
|
BASE_URL
https://v320.staging.saleor.cloud/dashboard/
|
API_URL
https://v320.staging.saleor.cloud/graphql/
|
POOL_NAME
3.20 Staging
|
POOL_INSTANCE
https://v320.staging.saleor.cloud/
|
BACKUP_NAMESPACE
snapshot-automation-tests-3.20
|
SNAPSHOT
backup_id=a3QvCLnf, version=3.20.33, name=snapshot-automation-tests-3.20
|
SALEOR_CLOUD_SERVICE
saleor-master-staging
|
🎭 Playwright Run Summary
118 passed (5.4m)
|
🎭 Playwright Run Summary
1 failed
[e2e] › attributes.spec.ts:165:7 › TC: SALEOR_128 User should be able to edit existing e2e product attribute to be updated 1 attribute @e2e @attributes
118 passed (6.0m)
|
Artifacts
Produced during runtime
Name | Size | Digest | |
---|---|---|---|
all-blob-reports
Expired
|
7.03 MB |
|
|
html-report--attempt-1
Expired
|
8.36 MB |
|