Dive into the latest Playwright 1.49 release with Stefan Judis, Playwright ambassador, as he discusses "toMatchAriaSnapshot", a new assertion for end-to-end page validations. In this video, Stefan discusses using recommended Playwright locators, the importance of ARIA and accessibility in end-to-end testing and demonstrates the new "toMatchAriaSnapshot" assertion.

Can AI generate good Playwright code? Join Stefan as he explores AI-driven Playwright scripting, using tools like the language models ChatGPT and Claude. Watch as he demonstrates the capabilities of Playwright's 'codegen' command and pits it against AI-generated test scripts. Despite initial skepticism, the results from AI were surprising!

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.

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.

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.

Learn how to optimize your Playwright end-to-end testing with additional `playwright test` command line options to run only failed tests, make Playwright Git-aware, or avoid running `test.only` in CI/CD. Got questions or tips?