Skip to main content

Playwright Check Suites are not working as expected

I’ve been trying to transition my tests from Browser Checks to the new Playwright Check Suites, but I’ve encountered multiple critical issues. The Playwright Check Suite setup prevents tests from running locally, execution is noticeably slower than Browser Checks, and scalability is essentially impossible. Even when I split execution into multiple suites with only ~75 scenarios each, nearly half of the runs either never complete and fail with “test run was cancelled”, or throw “out of memory” errors.

Realistically, this means each suite can handle how many scenarios? maybe 2–3 before becoming unstable? Which makes the feature unusable for a project with even ~500 tests.

The logs explicitly state “if you encounter this error again, reach out to support,” but support responses have been minimal or completely absent.

Given the current pricing of $500–700/month, the platform becomes very difficult to justify. At this point, it would be far more efficient to maintain a custom runner and execute via GitHub Actions with free, configurable Allure reporting rather than continuing to invest in Checkly.
Most likely next year we won’t be using checkly at all

Status: Completed2 comments

Log in to comment and vote

Comments2

  • Hervé Labas

    Team•

    Jul 23

    Closing this one one for now: since this post, we’ve made significant improvements to memory management and performance to ensure Playwright Check Suites would support these kinds of scenarios.

    If specific issues persist, feel free to open new ones and we’ll be more than happy to assist 🙏

  • Alberto Gomez

    •

    Dec 9, 2025

    hey Viktar, thanks so much for the feedback. We are looking into it with full attention. We know some existing Checkly users are finding a bumpy road when transitioning from Browser checks to Playwright Check Suites, and we are working to ease that path. I know our Playwright Product Manager has reached out to you to capture all your feedback, let’s continue the conversation to make sure we can deliver a swift satisfactory solution to that problem.