> ## Documentation Index
> Fetch the complete documentation index at: https://checklyhq.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.
# Playwright Check Suites
> Run your Playwright end-to-end test suite as synthetic production monitoring.
## What are Playwright Check Suites?
**Playwright Check Suites turn your Playwright end-to-end tests into production monitors.** Run entire test suites, specific projects, or tagged tests globally without modifying your existing code or configuration.
**Known limitations**: Each check run has a maximum execution time of 30 minutes.
**Use Playwright Check Suites to:**
* Turn E2E tests into global synthetic monitors
* Monitor complex user workflows across browsers and regions
* Detect issues in critical business processes
* Verify functionality after deployments
## How Playwright Check Suites Work
Choose which tests to turn into monitors using Playwright projects or tags from your existing configuration.
Specify the locations to run the check from, and set its frequency
Run selected tests on schedules from global locations with performance tracking and detailed reporting.
Receive notifications when tests fail or performance degrades.
## Test Selection
Control which tests run as monitors using:
* **Projects**: Select browser and project configurations from your Playwright config with `pwProjects`
* **Tags**: Choose tests marked with specific tags (e.g., `@critical`, `@smoke`) with `pwTags`
* **Combinations**: Mix tags and projects for precise control
* **testCommand**: Use `npx playwright test ...` to select the tests you want to create a monitor for, using playwright flags like `--grep-invert` or `--projects`
Configure test selection in your `checkly.config.ts` file:
```typescript checkly.config.ts theme={null}
export default defineConfig({
checks: {
playwrightChecks: [
{
name: "Marketing Environment",
logicalId: "environment-marketing-suite",
// Select the tests defined in
// the `environment-marketing` Playwright project
pwProjects: ["environment-marketing"],
},
{
name: "@critical tests",
logicalId: "critical-tests",
// Select tests tagged as `@critical`
pwTags: ["@critical"],
},
{
name: "customTestCommand",
logicalId: "custom-testCommand-critical-no-smoke",
// Select tests not tagged as `@smoke` and tagged as @critical
testCommand: "npx playwright test --grep-invert @smoke --grep @critical"
},
],
},
})
```
Learn more about [test organization strategies](/detect/synthetic-monitoring/playwright-checks/test-organization) for selecting and grouping tests.
## Monitoring Configuration
Customize how your checks run:
* **Frequency**: Schedule runs at regular intervals
* **Locations**: Deploy to multiple global regions
* **Alerting**: Set up notifications and escalation
* **Dependencies**: Use private packages and custom registries (see [custom dependencies](/detect/synthetic-monitoring/playwright-checks/custom-dependencies))
## Getting Started
Deploy your first Playwright Check Suite
Construct configuration options and examples
Organize checks with groups
Use private packages and custom registries