** Running on a schedule, from 20+ locations!

We’re thrilled to announce that Playwright Check Suites are now Generally Available (GA). Bringing full Playwright test suite support to your monitoring workflows, with a native developer experience and new visibility into cross-browser, cross-project test execution.

The feature request with most upvotes in Checkly’s history? 📬 Shipped. And we went way beyond it.

Create your first Playwright Check Suite today.

It’s a major milestone in uniting E2E testing and active monitoring for teams like yours.

💡 What’s new in Playwright Check Suites?

📁 Full playwright.config.ts or (.js) support

(This is how E2E and monitoring finally get on the same page)

Check Suites now respect global Playwright config files — giving you full control over:

• Viewport sizes

• Global setup/teardown

• storageState

• Screenshot, trace, video toggles…

🧠 Native Playwright test execution

No wrappers. No rewrites. Just run your existing Playwright tests as scheduled checks. Support includes:

• Projects (great for browser, env, and auth separation)

• Multi-browser (Chromium, Firefox, WebKit)

• Mobile device emulations (hi you, iphone-12, we’ve seen you often during the beta phase!)

• Private/public npm dependencies

• Feature-rich tests with setup hooks, fake devices, media access, and network mocking

• Use a custom testCommand to make each Check suite, completely yours.

📊 Granular test metrics in Check Overview

The check overview now shows per-test and region execution duration and flaky test insights. Duration graphs filter down based on your selected views for a clean, consistent UX.

🔎 Detailed results views

The new check result page shows exactly where failures happened — across browsers, projects, or both — with inline links to:

• The line of code that failed

• Traces, videos, screenshots, and snapshots associated.

• Logs scoped to the failed test only

• Slow tests

📁 Flat project view

A new, test-centric overview lets you browse tests across all projects in a single flat list, improving discoverability and reducing navigation friction.

🚀 Optimized for real-world Playwright setups

We support large test files, multi-file suites, custom test organization, Playwright tags (e.g. @smoke, @auth-only), and test reuse across teams and environments.

📈 Performance comparisons across projects

You can compare test performance per browser per project — and yes, it looks like Firefox is winning in speed for our docs site now hosted with Mintlify, who knew. 👀

🧩 In a gist

With Playwright Check Suites, you can now:

• Reuse your existing Playwright test suites 1:1 as production-grade, scheduled checks.

• Adopt monitoring faster — no need to split dev/test/monitoring logic.

• Run the same tests across multiple environments, browsers, and teams with full alerting control.

• Debug and iterate faster with rich execution insights and direct links to failure points.

This is the monitoring experience we wished existed when building complex frontend apps with confidence.

⚙️ What’s next?

Local Playwright test reporter

Debug your checks locally with the same fidelity you get in the cloud, using the same sharp view we have on Playwright Check Suite results!

Thanks to everyone who requested and upvoted this (👋 @Younes Jallouli )— the feedback helped shape what Check Suites became.

Ready to try it?

Head over to your Checkly dashboard and create your first Playwright Check Suite — or reach out opening a support chat, if you want early access to the reporter!

Happy monitoring!

Questions or feedback? Join our Slack community!