At Checkly we’re always trying to help our users find and resolve issues 10x faster, and the OpenTelemetry project wants to enable more observability with open standards. I’m excited to share Checkly Traces, our new tracing solution built on OpenTelemetry, and how it can help you find the root cause of problems in real time.

In today's video, we're exploring the fact that Playwright doesn't type check your code when using TypeScript. We'll explore what this means and discuss why this could be an issue, especially for larger projects. Then we set up type checking and add "typescript-eslint" to strengthen and improve your Playwright code. Join us for this deep dive and leave any questions or comments below. Stay tuned for more Playwright tips!

Join Nočnica Mellifera for the Checkly Kick-start. You'll learn: How to get started and write your first page monitors — Anyone can monitor their site with Checkly, and you'll get a demonstration on getting started. Best Practices for monitoring — From monitoring as code workflows to alert configurations based on your SLA, learn how experienced professionals use synthetic monitoring. Advanced skills for automation — Ever wanted to check your site by comparing screenshots? Or create checks that simulate network slowdown? Learn how to simulate complex scenarios with Checkly and Playwright.

In this video, we dive into Playwright's "page.goto()" and understand why it could be slowing down your end-to-end tests. We start with an example script and then walk you through the Playwright UI mode to understand how resource loading can delay the "page.goto()" call. We also look into the different "waitUntil" configurations and check how they affect the speed of your tests. Enjoy, and drop any questions or comments below!