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: docs/TESTING.md
+10Lines changed: 10 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -18,6 +18,8 @@ To execute end-to-end tests normally (i.e. not in debug mode), use the following
18
18
npm run test:e2e
19
19
```
20
20
21
+
### Troubleshooting
22
+
21
23
If this is your first time running the tests you may need to install the Playwright browser drivers:
22
24
23
25
```sh
@@ -26,6 +28,14 @@ npx playwright install
26
28
27
29
If something fails read the Playwright error carefully as it usually describes a quick fix. You can also look for the error in the [Playwright GitHub Issues](https://github.com/microsoft/playwright/issues) if you need more help.
28
30
31
+
If you continue to get unexplained failures another thing you can try is [limit the number of workers](https://playwright.dev/docs/test-parallel#limit-workers) in [playwright.config.ts](../playwright.config.ts):
32
+
33
+
```json
34
+
{
35
+
"workers": 1
36
+
}
37
+
```
38
+
29
39
### Debug
30
40
31
41
The debug test script runs the [Playwright inspector](https://playwright.dev/docs/inspector), which runs in headed debug mode so you can step through tests and watch them as they execute.
0 commit comments