Operations | Monitoring | ITSM | DevOps | Cloud

New In Playwright 1.51 - Can AI Fix Failing Tests With The New Error Prompt?

In this episode, Stefan Judis, Playwright ambassador, explores the new 'Copy as prompt' feature in Playwright 1.51. This feature allows you to copy a pre-filled LLM prompt with all the context of a failing test case. Does this mean that AIs can take over and magically fix all the failing tests? Let's find out!

Combine Fixtures & Page Object Models for DRYer Test Code in Playwright

If you're using Playwright for end-to-end testing or synthetic monitoring with Checkly, you've likely considered reusing your test code across different test cases. A common approach for this is using Page Object Models (POMs). However, if you're like me, you might have mixed feelings about POMs—while they help organize your code, they can sometimes feel cumbersome to set up and maintain.

Integrate Checkly with Render for more reliable production environments

With Render’s announcement this week of their new webhook integrations triggered by Render events, I wanted to explore how the integration between Render and Checkly can help ensure more reliable production services for your users. Render is a cloud application platform that enables developers to deploy and scale their apps without needing to manage infrastructure.

Reducing MTTR: Why Speed Matters for B2B SaaS Companies

For B2B SaaS companies, downtime isn’t just an inconvenience—it’s a direct threat to customer satisfaction and revenue. Unlike consumer applications, they serve a mix of power users pushing the system to its limits and new users expecting a seamless experience from day one. Reliability isn’t just about keeping services online—it’s about ensuring every user interaction runs smoothly. A minor hiccup for one customer might be a major disruption for another.

Why you should never use page.waitForTimeout() in Playwright

Playwright isn’t a testing framework. Sure it’s got assertions, scripted behaviors, even controls over environments. But testing isn’t Playwright’s only purpose. Playwright is an automation tool. It can carry out any browser-based action consistently, and carry out instructions robustly. Locators for buttons and other elements aren’t visual or CSS class-based, but based on ARIA role, and even small styling changes won’t make the scripted action fail.

Why you shouldn't run tests sequentially

Frequently in support conversations and posts on Playwright forums, a problem has come up that’s a little bit hard to describe, but comes down to synchronous testing: developers writing a series of Playwright tests that operate on the assumption that one of the tests will either run first or run last, and perform the function of a setup and cleanup script.