Operations | Monitoring | ITSM | DevOps | Cloud

Checkly

How to detect broken links with Playwright

One of our Slack community members recently asked if they could use Playwright and Checkly to detect broken links on their sites. They certainly can, and the answer to this question covers so many different Playwright concepts that it makes a perfect case for sharing Playwright features with the community. Let's unveil some links going nowhere! If you prefer the video version of this tutorial,

How to detect broken links with Playwright Test

Join Stefan Judis in this Playwright tutorial, where he explores detecting broken links using Playwright and/or Checkly. Stefan covers essential techniques such as soft assertions, crafting custom error messages for clearer debugging, and using page context-aware requests to check for URL status codes. Whether you're dealing with empty links, nonexistent domains, or 404 errors, this video provides all the tools needed to enhance your testing strategy effectively.

How to test and monitor your APIs with Playwright

You probably know that Microsoft’s Playwright is a solid tool for end-to-end testing, enabling you to control headless browsers and check essential user flows. But did you know that you can also use Playwright for API testing? If you didn’t, then this guide is for you. 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).

How to apply Playwright test steps with TypeScript decorators

You can write Playwright end-to-end testing code using JavaScript or TypeScript. Which one should you choose? When I started writing my first automated browser tests, I went with JavaScript because I couldn't be bothered with the type wrangling. I just wanted to get something off the ground quickly. YOLO, right? Today, though, there are two reasons why I last wrote a JavaScript-first Playwright test a very long time ago.

Apply Playwright test steps with TypeScript decorators

Join Stefan Judis as he explores the concept of decorators in Playwright TypeScript code. Learn how decorators can streamline your coding process, improve test readability, and save you time. In this tutorial, Stefan will demonstrate how to implement decorators within Playwright page object models, starting from scratch. He provides practical examples and insights into decorators, a feature not yet standard in JavaScript but available in TypeScript.

Software Deployment Best Practices for Modern Engineering Teams

Adopting best practices for software deployment is essential to maintaining a high standard of quality, minimizing downtime, and ensuring that your applications meet user expectations. Here are five best practices to help you deploy your software more securely and reliably.

Make Your End-to-end Tests More Stable with Playwright's User-first Selectors

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.

From Basic Monitoring to Modern Observability: Shifting Right and Observability as Code

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.

How to Speed up your Playwright Tests with shared "storageState"

Join Stefan Judis, Playwright Ambassador, as he shows you how to speed up your Playwright test suite execution time for apps behind a login. Usually, login-walled products require you to log in for every test case. However, by implementing project dependencies, setting up a project, and pairing everything with the storage state, you can log into your app once and then reuse the browser and storage state. This setup equips your subsequent tests with essential cookies and browser state, saving time and effort by avoiding repetitive login actions.