Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -142,7 +142,7 @@ When running tests from the editor page, trace files are always available for do
regardless of whether the check is passing or failing. For scheduled check runs traces are only preserved when the check failed.

## Video recordings
When a `@playwright/test` test case fails, Checkly will record a video for each page navigation and make it available in the UI. It is a great tool to get a first look of the actions and their outcome to quickly identify what failed, and to visualize regressions.
When a `@playwright/test` test case fails, Checkly will record a video for each page and make it available in the UI. It is a great tool to get a first look of the actions and their outcome to quickly identify what failed, and to visualize regressions.

Here's an example of a Playwright Test script that fails, and provides a video of the test sequence.

Expand Down
4 changes: 2 additions & 2 deletions detect/synthetic-monitoring/browser-checks/timeouts.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -61,10 +61,10 @@ test('add item to wishlist', async ({ page }) => {
</CodeGroup>


### Your check run has reached the maximum run time of 240000 ms.
### Timed out waiting 240s for the test suite to run

In this case, your script is hitting Checkly's 240s total Browser check timeout. This can't be configured and is in
place to prevent checks from running way longer than acceptable. No assets will be available for review after the check has gone over the maximum run time. If you encounter this, try to make your check shorter by following [best practices](/learn/playwright/writing-tests/). Additionally, to ensure your assets are saved, please set a test timeout lower than the Browser check execution timeout.
place to prevent checks from running way longer than acceptable. The test that was still running at the limit has no trace or video. If you encounter this, try to make your check shorter by following [best practices](/learn/playwright/writing-tests/). Additionally, to ensure your assets are saved, please set a test timeout lower than the Browser check execution timeout. Scripts that don't use `@playwright/test` report this limit as `Your check run has reached the maximum run time of 240000 ms.`

### Timeout 20000ms exceeded

Expand Down
11 changes: 11 additions & 0 deletions detect/synthetic-monitoring/browser-checks/troubleshooting.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -49,6 +49,17 @@ canonical: 'https://www.checklyhq.com/docs/detect/synthetic-monitoring/browser-c
3. Use parallel execution where possible
4. Monitor and alert on performance degradation

</Accordion>

<Accordion title="Missing traces or videos">
**Issue: A result has no trace or video, or some pages have no video**

**Solutions**:
1. Check whether the run failed. Scheduled runs keep the trace and video only when the check fails. Runs from the editor keep them whether the check passes or fails, and so do runs you record with `npx checkly test --record` or `npx checkly trigger --record`. See [Viewing trace files](/detect/synthetic-monitoring/browser-checks/playwright-support#viewing-trace-files).
2. Don't rely on the `trace` and `video` options in your Playwright configuration. Browser checks ignore them, so you can't keep artifacts for passing scheduled runs or turn off video recording. To control them, use a [Playwright Check Suite](/detect/synthetic-monitoring/playwright-checks/overview) and [set `use.trace` and `use.video`](/detect/synthetic-monitoring/playwright-checks/configuration#checkly-applied-playwright-settings).
3. Open pages from the test's own `page` or `context` fixture. Playwright records one video per page in that context. Pages from a context you create with `browser.newContext()` have no video. See Playwright's [videos guide](https://playwright.dev/docs/videos).
4. Set a test timeout below the 240-second run limit, for example `test.setTimeout(210000)`. A test that times out on its own test timeout keeps its trace and video. A test still running when the check reaches the run limit is stopped without them. See [Browser check timeouts](/detect/synthetic-monitoring/browser-checks/timeouts).

</Accordion>

## Error Handling and Debugging
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -121,16 +121,18 @@ Checkly applies these defaults only when you do not set the option yourself:
|-------------------|-----------------|
| `workers` | `4` |
| `retries` | `2` |
| `use.trace` | `on-first-retry` |
| `use.video` | `on-first-retry` |
| `use.screenshot` | `on-first-retry` |

Your Playwright config or `testCommand` value takes precedence for these options.

Checkly always records a trace, and keeps the trace file only when your `use.trace` setting would have produced one. With the defaults, a test that passes on its first attempt keeps no trace or video, and a failing test keeps them only for its first retry. With `retries` set to `0`, a failing test keeps neither. To keep them for every run, set `use.trace` and `use.video` to `on`. To turn off video recording, set `use.video` to `off`.

Checkly enforces these options for every run. User configuration does not override them:

| Playwright setting | Checkly behavior |
|--------------------|------------------|
| `use.trace` | `on` for every run |
| User agent | Checkly appends a [user-agent suffix](/platform/allowlisting-traffic#default-checkly-user-agent) |

Checkly supports Playwright's [`globalTimeout`](https://playwright.dev/docs/api/class-testconfig#test-config-global-timeout). Use it to control the maximum duration of the Playwright suite after `npx playwright test` starts.
Expand Down
Loading