At the top of the pyramid: Playwright testing at scale
summary
Project grows from zero to 20,000 lines of Playwright tests in a year, using Playwright features like the trace viewer, AI-assisted prompts, and a step decorator to make reports readable via Allure Reports. Team enforces isolation with full parallel mode and increases workers (reducing test shards from 51 to 17), fixes flaky assertions by adopting eslint-style best practices, and speeds suites with the network cache plugin, saving about ten minutes across 200 slow tests while surfacing real backend bugs. Results drive refactors: upgrades, feature-sliced design, and faster TypeScript migration.
AI-written summary · about
chapters (12)
- 0:00Introduction to Playwright
- 3:14Testing in a regulated domain
- 5:42Choosing a testing strategy
- 7:52Testing mushroom explained
- 8:36Fixing flaky tests with ESLint
- 9:41Handling test dependencies
- 11:25Improving test reports with step decorator
- 12:31Using Allure Reports
- 13:15Optimizing test execution speed
- 14:22Network caching for performance
- 15:47Testing mushroom recap
- 16:30Unexpected benefits of testing
related talks
21mAt the top of the pyramid: Playwright testing at scale
49mReal World Lessons from Scaling Test Automation
29mPlaying your tests wright
12mPlay It Right With Playwright
51mAdvanced Playwright Techniques for Flawless Testing
14mAdvanced Playwright Techniques for flawless testing
42mMichal Slezak: Creating a Framework with Playwright - How to Do It Right?
11mHow to make cheap e2e tests