Playwright Myths Busted: Speed, Flakiness, Production Monitoring & AI Test Generation

Playwright is too hard, too slow, and too flaky — right? In this webinar, Stefan busts six common end-to-end testing myths and shows how to reuse your Playwright tests as production monitors with Checkly.

He covers codegen, trace viewer, UI mode, flakiness root causes (and fixes), and a quick look at Playwright MCP for AI-assisted test generation.

🔗 Checkly — https://www.checklyhq.com
🔗 Playwright docs — https://playwright.dev

00:00 Webinar kickoff

00:07 Housekeeping and intro

01:27 What is Checkly

02:14 Why Playwright matters

03:14 One codebase lifecycle

04:23 Running tests as monitors

06:04 Six myths overview

07:02 Myth 1 — too hard

07:56 Codegen quick start

10:21 Debugging with traces

11:29 UI mode and AI fixes

13:57 Myth 2 — too slow

14:32 Speeding up navigation

17:21 Actionability and assertions

20:28 Myth 3 — flaky tests

21:46 Root causes of flakiness

22:43 Flaky demo login flow

23:59 Handling popups reliably

27:03 Common visibility mistake

27:45 Avoid redundant assertions

28:21 Ditch hard timeouts

28:56 Accessibility-first locators

31:10 Retry with toPass

33:40 Playwright too-fast gap

37:02 Fix UX to fix flakes

39:02 Run tests in production

41:02 Scheduled monitoring deploy

43:42 AI writes Playwright tests

49:37 Quality is everyone's job

50:42 Wrap-up and Q&A

#checkly #playwright #testing #monitoring