You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/playwright-testing/includes/include-playwright-portal-view-test-results.md
+11-3Lines changed: 11 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,15 +7,23 @@ ms.date: 09/23/2024
7
7
---
8
8
9
9
10
-
1. To see the test results and artifacts on Playwright portal, open the link generated at the end of test run in the console. The portal contains the CI information, test run status, and commit ID associated with the test run.
10
+
1. After your test run completes, a link to the Playwright Portal is generated. Click this link to view detailed test results and associated artifacts. The portal displays essential information, including:
11
+
- CI build details
12
+
- Overall test run status
13
+
- The commit ID linked to the test run
11
14
12
15
:::image type="content" source="../media/include-playwright-portal-view-test-results/playwright-testing-open-test-run.png" alt-text="Screenshot that shows list of tests in the test run." lightbox="../media/include-playwright-portal-view-test-results/playwright-testing-open-test-run.png":::
13
16
14
-
3. Open any failed test to see all the required information to troubleshoot. Switch between retries, see error logs, test steps, and attachments such as screenshots and video. Navigate to the trace viewer from here.
17
+
3. The Playwright Portal provides all the necessary information for troubleshooting. You can:
18
+
- Switch between retries.
19
+
- View detailed error logs, test steps, and attached artifacts such as screenshots or videos.
20
+
- Navigate directly to the **Trace Viewer** for deeper analysis.
15
21
16
22
:::image type="content" source="../media/include-playwright-portal-view-test-results/playwright-testing-open-test.png" alt-text="Screenshot that shows the preview of a test" lightbox="../media/include-playwright-portal-view-test-results/playwright-testing-open-test.png":::
17
23
18
-
4. Use the trace viewer to visually step through your test execution, or use the timeline to hover over steps and reveal the page state before and after each action. Detailed logs, DOM snapshot, network activity, errors, and console output are available at each test step.
24
+
4. The Trace Viewer allows you to step through your test execution visually. You can:
25
+
- Use the timeline to hover over individual steps, revealing the page state before and after each action.
26
+
- Inspect detailed logs, DOM snapshots, network activity, errors, and console output for each step.
19
27
20
28
:::image type="content" source="../media/include-playwright-portal-view-test-results/playwright-testing-trace-viewer.png" alt-text="Screenshot that shows the trace viewer" lightbox="../media/include-playwright-portal-view-test-results/playwright-testing-trace-viewer.png":::
Copy file name to clipboardExpand all lines: articles/playwright-testing/quickstart-generate-rich-reports-for-tests.md
+13-3Lines changed: 13 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -45,10 +45,20 @@ This generates `playwright.service.config.ts` file which serves to:
45
45
46
46
If you already have this file, the package asks you to override it.
47
47
48
-
Once you have the `playwright.service.config.ts` file, disable cloud-hosted browsers.
48
+
To use only reporting feature for the test run, disable cloud-hosted browsers by setting `useCloudHostedBrowsers` as false.
49
49
50
50
```typescript
51
-
useCloudHostedBrowsers: false
51
+
exportdefaultdefineConfig(
52
+
config,
53
+
getServiceConfig(config, {
54
+
timeout: 30000,
55
+
os: ServiceOS.LINUX,
56
+
useCloudHostedBrowsers: false// Do not use cloud hosted browsers
57
+
}),
58
+
{
59
+
reporter: [['list'], ['@azure/microsoft-playwright-testing/reporter']], // Reporter for Microsoft Playwright Testing service
60
+
}
61
+
);
52
62
```
53
63
Setting this as `false` ensures that cloud-hosted browsers are not used to run the tests. The tests run on your local machine but the results and artifacts are published on the service.
54
64
@@ -144,7 +154,7 @@ Test report: https://playwright.microsoft.com/workspaces/<workspace-id>/runs/<ru
144
154
```
145
155
146
156
> [!CAUTION]
147
-
> Depending on the size of your test suite, you might incur additional charges for the testminutes beyond your allotted free test minutes and free test results.
157
+
> Depending on the size of your test suite, you might incur additional charges for the testresults beyond your allotted free test results.
148
158
149
159
## View test runs and results in the Playwright portal
Copy file name to clipboardExpand all lines: articles/playwright-testing/quickstart-run-end-to-end-tests.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -194,7 +194,7 @@ To run a single Playwright test in Visual Studio Code with Microsoft Playwright
194
194
You can now run multiple tests with the service, or run your entire test suite on remote browsers.
195
195
196
196
> [!CAUTION]
197
-
> Depending on the size of your test suite, you might incur additional charges for the test minutes beyond your allotted free test minutes and free test results.
197
+
> Depending on the size of your test suite, you might incur additional charges for the test minutes and test results beyond your allotted free test minutes and free test results.
0 commit comments