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
Please authenticate to join the conversation.
In Review
💡 Feature Request
Playwright
3 months ago

Viktar Zhuk
Get notified by email when there are changes.
In Review
💡 Feature Request
Playwright
3 months ago

Viktar Zhuk
Get notified by email when there are changes.