Operations | Monitoring | ITSM | DevOps | Cloud

Add global beforeEach / afterEach hooks using Playwright automatic fixtures

Join Stefan Judis, Checkly's Playwright ambassador, as he shows you how to make your end-to-end testing life easier using Playwright's automatic fixtures. Learn how to implement global "beforeEach" and "afterEach" test hooks to add runtime annotation and JavaScript exception monitoring without repeating yourself across spec files.

Checkly Changelog: New Features and Updates - Traces, Visual Regression Checks, and Degraded States

Join María and Nočnica as we go over three major new features from Checkly: Checkly Traces - integrate OpenTelemetry data from your stack with synthetic monitoring traces Visual Regression Checks - Check for pixel-by-pixel changes to your website Degraded Checks - want to note a problem but don't want it to trigger alerts like a failing check? Try soft assertions and the 'degraded' state.

How to control time zones and timeouts in Playwright

Join Stefan Judis (Playwright Ambassador) as we explore advanced testing strategies for time zones and timers using Playwright. You'll learn about seamless time zone testing techniques and how to use Playwright's Clock API to manage timers effectively. What we'll cover: Time Zone Testing: Learn how to test across multiple time zones with Playwright to ensure your applications perform consistently worldwide. JavaScript Timers: Discover how to control and test JavaScript timeouts using the Clock API, enhancing the reliability of your scripts.

Five Playwright CLI features you should know

Thanks to Microsoft's Playwright, running end-to-end tests with real browsers is quickly done. Initialize a new Playwright project, install all the dependencies, and off you go! Then, any new headless browser test run is only one npx playwright test away. But have you checked all the test command's CLI options? playwright test includes a few real gems to help you create better tests faster. Let me share a mixed bag of my favorite CLI tricks in this post.

How to parameterize Playwright projects

In a previously released YouTube video, I explained how and why Playwright fixtures perfectly match with page object models. Combining the two allows you to hide setup instructions and keep your tests clean. Page object models no longer have to be initialized in every test case. To be upfront — I'm a fixture fanboy! But what if you need to pass additional configuration to your page object models? When options are hidden in a fixture, you can't configure how a class is initialized, right? Wrong!

How to parameterize and configure your custom Playwright fixtures

Join Stefan Judis in this Playwright tutorial, where he explains how to make your custom Playwright fixtures configurable using "option fixtures". Stefan briefly explains the fixture concept but then focuses on creating an option fixture configurable on a global, project, and spec file basis.

Attach Screenshots to Your Playwright Test Reports

Today I want to show you how you can attach your screenshots directly to Playwright's test reports. Imagine you have a simple Playwright test that navigates to Checkly. You take a screenshot and store it in screenshots/home.png. Then, you click a link in the main navigation, expect a specific heading to be visible, and take another screenshot. When you run this test using npx playwright test, the test passes, and you find the screenshots in the /screenshots directory.

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.