Operations | Monitoring | ITSM | DevOps | Cloud

We all check the video first, let's go further to find out why our Playwright test failed.

Find yourself writing the steps of logging in every single Playwright test?   Instead of going through the login sequence, we can take a snapshot of the browser of all the cookies and everything and just log in once.

In this video, Stefan Judis, Playwright ambassador, explains the power of Playwright fixtures while running tests in JavaScript or TypeScript. Learn how to streamline your test setup, remove repeated code, and leverage custom fixtures for cleaner and more efficient end-to-end tests. By the end of this video, you'll have a clear understanding of why you should use Playwright's native architecture to structure your testing project.

This video features a joint session hosted by the Checkly team in collaboration with Mezmo. We discuss current practices and challenges in web application monitoring. The session explores practical strategies, shared experiences from both teams, and insights into how modern engineering teams are approaching observability and reliability at scale.

How to diagnose failures with a Playwright trace: https://www.checklyhq.com/guides/reading-traces/

Playwright fixtures: https://youtu.be/2O7dyz6XO2s

Checkly CLI Import is now in Beta. If you started adding your monitors through the Checkly UI and now want to scale and move to Monitoring as Code, you can do this effortlessly - by using our new Checkly Import command.

Join Nočnica and Filip for best practices on using your Playwright tests across your SDLC.