Skip to main content
Monitoring as Code: Learn more about the Playwright Check Suite Construct.
Playwright Check Suites are currently in Beta. Join the Slack community to get live updates on feature development and get help getting started.

​
What are Playwright Checks?

Playwright Check Suites enable you to run entire Playwright end-to-end test suites, Playwright projects or tagged tests as pre-production tests and global production monitors, without rewriting your tests and configuration. Unlike Browser Checks, Playwright Check Suites are not limited to a single test spec and our preinstalled runtime dependencies. Playwright Check Suites enable you to run Playwright projects complete with all of your required dependencies, private packages, storage, data, and more, and enable you to detect issues with your applications or services even in the most complex scenarios.
Playwright Check Suites test result
Playwright Check Suites are the native way to run Playwright in production and support the full Playwright API and ecosystem, meaning you can use your existing tests and playwright.config.ts files as is. Playwright Check Suites are perfect for:
  • Converting existing E2E tests into monitoring
  • Testing complex user workflows across multiple browsers
  • Monitoring critical business processes
  • Validating application functionality after deployments

​
How Playwright Checks Work

1

1. Test Discovery

Playwright Check Suites analyze your Playwright configuration and test files to understand your existing test structure.
2

2. Selective Monitoring

Use tags and projects to define monitoring scope, choosing which tests become production monitors.
3

3. Global Deployment

Deploy your selected tests to run from multiple worldwide locations for comprehensive coverage.
4

4. Continuous Monitoring

Execute tests on schedules with performance tracking and detailed reporting.
5

5. Alert Integration

Receive notifications when tests fail or performance degrades, keeping your team informed.
Runtime Limits: During Beta, Playwright Checks can run up to 20 minutes per execution. This limit can be adjusted based on feedback.

​
Test Selection

Control which tests become monitoring checks using:
  • Projects: Choose browser configurations from your Playwright config
  • Tags: Select tests marked with specific tags (e.g., @critical, @smoke)
  • Combinations: Mix tags and projects for precise test selection
checkly.config.ts
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"],
      },
    ],
  },
})
The Playwright Check Suite runner will use the pwProjects and pwTags values to configure the native Playwright Test CLI run. pwProjects reflects the --project and pwTags the --grep CLI options.

​
Monitoring Configuration

Customize monitoring behavior with:
  • Frequency: From every minute to custom schedules
  • Locations: Choose from global monitoring regions
  • Alerting: Configure team notifications and escalation
  • Groups: Organize related checks for management
  • Dependencies: Support for private packages and custom registries

​
Getting Started

Ready to turn your Playwright tests into monitoring? Start with our quickstart guide to get running in 5 minutes.

Quickstart Guide

Get from zero to deployed monitoring in 5 minutes

Construct Reference

Complete configuration options and examples

Add to Group

Organize checks with groups for better management

Custom Dependencies

Use private packages and custom registries
⌘I