Operations | Monitoring | ITSM | DevOps | Cloud

March 2024

Avoid flaky end-to-end tests due to poorly hydrated Frontends with Playwright's toPass()

In this video we'll dive into the world of flaky tests in Playwright and synthetic monitoring with Checkly. We examine a site with poor Frontend hydration patterns, their effect on test stability, and how to work around them. Learn how to avoid using artificial delays and implementing a retry mechanism with Playwright's 'toPass()' method to achieve stable testing instead.

Add accessibility checks to your Playwright end-to-end tests

Join us in today's video as we dive into the world of web accessibility testing with "axe-core". "axe-core" is used in Google Chrome's lighthouse and is quickly integrated in your Playwright end-to-end tests. We'll integrate "axe-core/playwright", detect accessibility issues, attach these to test reports and even integrate accessibility checks in Checkly's synthetic monitoring thanks to a new beta runtime.

Running Your Playwright Tests in Parallel or in Sequence

Playwright offers robust capabilities for automating browser tests. A common question among developers, however, revolves around the best practices for structuring Playwright projects, especially when tests involve significant environment changes, resource creation, or database updates. This blog post describes strategies for running Playwright tests either in parallel or in sequence, optimizing your testing workflow for efficiency and reliability.

Improve Your Playwright Documentation with Steps

When you’re implementing automated testing, clarity and maintainability of test scripts are as crucial as the tests themselves. Playwright offers a feature that enhances the readability and ease of debugging of your tests: test steps. This article explores how to use test steps in Playwright to document your test cases effectively.

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.