Operations | Monitoring | ITSM | DevOps | Cloud

Checkly

Integrating Accessibility Checks in Playwright Tests with Checkly

Ensuring your web application is accessible is not just about compliance; it's about inclusivity. Tools like Google Chrome's Lighthouse provide a starting point for accessibility checks. but integrating these checks into your development workflow can significantly enhance the quality of your product. This post explores how to perform automated accessibility checks using Playwright and Checkly, leveraging the power of the axe-core library.

New in Playwright: detect and close unpredictable overlays with "addLocatorHandler"

Discover the latest feature of Playwright 1.42 — `page.addLocatorHandler`. If you're tired of randomly appearing cookie banners breaking your end-to-end tests or want to automatically close all these intercom widgets, this method is right up your alley. With `addLocatorHandler`, handling elements that randomly pop up becomes a breeze! In the video, we'll show you how the new Playwright method works in practice and why it makes end-to-end testing and synthetic monitoring so much easier.

Beyond APM: What Datadog Won't Tell You with Leon Adato of Kentik

APM tools promise a unified observability platform, yet they inherently focus on internal metrics, traces, and logs. This internal focus, while valuable, misses critical dimensions of the user experience and network performance that are essential for a complete understanding of application behavior in real-world scenarios. With Kentik you can dive deep into your network performance and find problems before they affect your users.

How to detect, test and monitor your Next.js API endpoints with the Checkly CLI

In this video, we explore how to use the Checkly CLI to programmatically test and monitor Next.js API endpoints. We'll create a dynamic setup that detects new API GET URLs and use GitHub actions to test preview API deployments and deploy API monitoring after production deploys.

Cultivating Your Tech Garden: Enriching APM with Synthetic Monitoring

Welcome to the Tech Garden, a place where our monitoring tools, like to diverse flora, contribute to a thriving digital ecosystem. Our journey starts with the foundational roots of Application Performance Monitoring (APM), crucial for initial growth and stability, like the roots beneath our fruit trees.

Broken windows: Why the 'Single Pane of Glass' is Impossible

It was only as I started to study information theory that I truly understood how nonsensically the computer worked in Star Trek: The Next Generation. Decades before voice assistants and at a time when only the most basic language parsing existed in practice, the computer on Star Trek could always give you the answer you wanted. No one ever spent any time clicking into multiple windows to find an answer, and the display always gave information that could be easily summarized in words.

How to run your Playwright end-to-end tests in SloMo

Sometimes you want to follow along your Playwright tests without starting a full debugging session. Learn in this video how to slow down your Playwright end-to-end tests, to see and watch exactly what's happening in your testing scripts. Use the "slowMo" launch option configuration to add delays inbetween all Playwright actions. More cool Playwright and Synthetic Monitoring tips coming your way soon!

How to end-to-end test and monitor your login flows with Playwright and Checkly

In this video, Stefan from Checkly demonstrates how to monitor a login and authentication flow using Checkly and Microsoft's Playwright. Stefan guides you through the entire process. If you're interested in end-to-end testing or synthetic monitoring, this video is for you. Drop a question below or leave a comment!

The Real Cost of Synthetic User Testing with AWS

Every time I share a project using SaaS tools, someone inevitably responds that they could do the same thing on their own home server ‘for free.’ I mention this not because it is annoying, since I would never go on social media at all if annoying responses were allowed to change my behavior, but because I think it points to a basic misconception that still affects DevOps practitioners today: the refusal to accurately estimate the real costs of self-managed solutions.