Discover essential Playwright CLI features that can streamline your testing process and learn how to leverage powerful flags like "--last-failed" to rerun failed tests efficiently, "--only-changed" for testing only modified files, "--repeat-each" to ensure test stability by running tests multiple times, "--forbid-only" to prevent accidental test suite limitations, and "--headed --workers 1" for enhanced debugging in UI mode. These tips will help you optimize your end-to-end testing workflow, making it more efficient and reliable.

Discover how to streamline your Playwright testing framework using fixtures and page object models for cleaner, more maintainable code. Learn to implement and configure custom Playwright options. This guide covers everything from basic fixture implementation to advanced configuration techniques, ideal for developers looking to optimize their Playwright projects.

Learn how to attach screenshots directly to Playwright test reports, centralizing all files in one place for an integrated view of test results.

Learn how to use Playwright and Checkly for effective broken link detection in your web applications and sites. This guide explains step-by-step how to extract links URLs and evaluate URL status codes in Playwright end-to-end tests.

tl;dr: Node by default doesn’t implement the Happy Eyeballs algorithm for web requests, and therefore if a server has a broken IPv6 address that responds first, it will usually fail. This is the story of how an otherwise working server was completely unavailable for users in a geographic region, and how in one very specific way Node doesn’t handle requests as well as an Opera browser from 2011. How we got here: the Checkly Coralogix integration By now you’ve heard of the Checkly Coralogix integration, part of a broader strategy at Checkly of embracing OpenTelemetry and using Checkly to give you insight into backend services’ performance. Released a couple of months ago, this integration lets you set some configuration options in Checkly to send our synthetic monitoring (a fancy term for scheduled end-to-end tests) traces to Coralogix. Once the integration is enabled you’ll see connected traces linked from the Checkly interface: A Checkly trace with a link to Coralogix And you can find

In this post, we’ll explore how Playwright can be used to test a GraphQL API (but don’t worry if you’re using REST; Playwright can handle any HTTP-based API). Let's dive into an example using the countries.trevorblades.com GraphQL API.

Use TypeScript decorators to streamline and structure your Playwright tests. Learn how to efficiently structure test steps and enhance your Playwright test reports with practical tips on implementing TypeScript decorators in page object models.

Discover essential software deployment best practices tailored for modern engineering teams. Learn how to streamline your deployment processes, enhance efficiency, and ensure successful rollouts with these expert strategies.

When testing and monitoring websites end to end with Playwright, choosing the right locators is crucial. Proper locators help create tests that are less flaky and more reliable. Let's explore user-first locators and how to filter locators for more robust tests. Example Scenario Consider a simple web page with a headline, a button, and a status update box. Clicking the button updates the status and throws confetti. Here's how we can test this. Why we don't want to find a page element with CSS selectors If you're used to some older systems for automation and page manipulation like JQuery, we might be tempted to use CSS selectors. If we inspect this page we'll find, sure enough, that there is a class applied to this button that should select it in the page. We could click this button in a test with a line like await page.locator("button.button-frontpage-style").click() and that would work, but it's not recommended. What is the problem with this approach? Our users look at the page and wan

A Journey Through Time From My Perspective I've been in the observability market long before it even had that name. Over the years, observability has undergone a significant transformation. As someone who has witnessed these changes firsthand, I can attest to the dynamic nature of this field. In the early days, it was largely about basic monitoring: tracking system metrics, lots of logs, and simple alerts. A typical setup would use Nagios or Zabbix (sometimes both), Cacti for charting system metrics, and lots of grep and vi for searching and reading log files split out of your monolith. This led in the mid-2000s to the foundation of various cloud-based SaaS platforms to help engineers do the job. Splunk for logging, AppDynamics, New Relic and Dynatrace for APM, Zabbix for infra, and later early 2010s Datadog with a clear Infrastructure and data consolidation mindset. Those products democratized access to the data and offered solutions to manage the various aspects of the later-called O

Standards in coding are not arbitrary; they are established from accumulated experience to prevent common pitfalls and enhance collaboration. In specific contexts, adhering strictly to these guidelines may not yield the best outcome. Our case, where we deferred loading a module until absolutely necessary, demonstrates a situation where performance gains outweighed the typical benefits of following best practices.

Discover how to speed up your Playwright tests by implementing 'storageState' to reuse browser session data across tests, reducing redundancy and test execution time. Learn setting up project dependencies and persisting session states to streamline your end-to-end testing process. This guide provides insights and code examples to optimize your Playwright testing suite, ultimately saving time and resources in your CI/CD pipeline.

We are very excited to announce our new feature Checkly Traces and our Series B funding round led by Balderton, alongside the participation of our existing investors Accel and CRV.

Learn how to enhance Playwright projects with TypeScript type checking and linting. Reduce errors, boost development speed, and avoid unnecessary CI/CD loops.

Learn the importance of observability, the challenges of traditional observability practices, and how to automate the setup with Observability as Code.