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
16 changes: 16 additions & 0 deletions detect/synthetic-monitoring/playwright-checks/configuration.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -239,3 +239,19 @@ If tests fail due to authentication issues:

- Verify environment variables are set correctly in Checkly. You can verify your environment variables using `npx checkly env ls`, or looking at your Global or Check's environment variables in the Checkly Webapp to ensure any `process.env.VARIABLE_NAME` call from your test is defined.
- For persistent authentication, use Playwright's [`storageState`](https://playwright.dev/docs/auth#reuse-authentication-state) feature.

**webServer configuration requires additional files**

When using `webServer` in your Playwright config, you need to include the server files in your check configuration:

- Add server files to the `include` parameter in your [Playwright check configuration](/constructs/playwright-check/#param-include)
- Include all files needed to start the server (e.g., server scripts, config files)
- Alternatively, skip `webServer` on Checkly and use your deployed URL: `...(process.env.CHECKLY ? {} : { webServer: { ... } })`

**No tests found**

If Playwright couldn't find any tests to run, this usually means a mismatch between your config and your test files:

- Verify your `--grep` pattern matches actual test tags or projects
- Verify the `testDir` path in `playwright.config.ts` matches the actual directory containing your test files
- Ensure path aliases (`~/`, `@/`) in imports are configured in your `tsconfig.json`, or replace them with relative paths
Original file line number Diff line number Diff line change
Expand Up @@ -189,4 +189,19 @@ If Checkly uses the wrong package manager:
If package installation exceeds time limits:

- Check for large dependencies that can be optimized
- Consider using a custom `installCommand` to install only required packages
- Consider using a custom `installCommand` to install only required packages

### Memory usage exceeded

If you see errors indicating that memory limits were exceeded during installation:

- Optimize your dependencies to reduce memory consumption
- Consider using a custom `installCommand` to install only necessary packages

### General installation failures

If you encounter general installation errors:

- Review the full error logs for specific issues
- Ensure all dependencies are compatible with the Node.js version used by Checkly
- Consider using a custom `installCommand` to handle complex installations
2 changes: 2 additions & 0 deletions detect/synthetic-monitoring/playwright-checks/timeouts.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -71,6 +71,8 @@ Failed to run install command
- Check if your registry is slow or has issues
- Update and commit your lock file

See the [Custom dependencies troubleshooting guide](/detect/synthetic-monitoring/playwright-checks/custom-dependencies#troubleshooting) for more detailed solutions.

### Global timeout exceeded

```
Expand Down