At the top of the pyramid: Playwright testing at scale
summary
From zero to 20,000 lines of Playwright tests covering 64 epics, the team turns failing, flaky suites into stable, readable checks by using the ESLint Playwright plugin to fix API misuse, grouping steps for clarity, and publishing Allure reports so backend teams can read failures. Running 200 tests in full parallel mode and tuning workers cuts pipeline time from 51 to 17 minutes, and using Playwright network cache recovers ~10 minutes by reusing expensive responses.
AI-written summary · about
chapters (14)
- 0:00Introduction and speaker intro
- 0:41What is Playwright
- 3:13Testing at Aton Healthcare
- 6:31Testing strategies overview
- 7:58Introducing testing mushroom
- 8:40First testing attempt failure
- 9:23Fixing flaky tests with ESLint
- 10:27Test dependencies and isolation
- 11:31Debugging test failures
- 12:13Improving test readability
- 14:33Slow tests blocking deployment
- 16:01Mocking without mocks
- 17:49Testing mushroom explained
- 18:11Wrap-up and key takeaways
related talks
18mAt the top of the pyramid: Playwright testing at scale
49mReal World Lessons from Scaling Test Automation
11mHow to make cheap e2e tests
29mPlaying your tests wright
12mPlay It Right With Playwright
40mMonitoring as Code: E2E Testing in Production with Playwright
48mHow We Tried to Introduce E2E Tests and Why It Failed
14mAdvanced Playwright Techniques for flawless testing