Real World Playwright Case Studies That Will Change Your Perspective!
summary
Large-bank case studies show Playwright replacing Selenium to run multiple user flows inside one Chromium process with browser contexts that cut memory and energy (claiming energy saved equivalent to an Amsterdam–Paris EV trip for one project). Using storageState to avoid 120 logins saves ~20–25s per test, mocking intercepts APIs to stabilize flaky backends, traces record DOM snapshots and timelines for lightweight debugging, and early proofs with Playwright agents plus GitHub Copilot begin automating locator selection and test generation.
AI-written summary · about
chapters (16)
- 0:00Playwright at ING Bank
- 1:27Selecting Playwright
- 2:11Green IT with browser contexts
- 7:31Login steps reduced
- 11:45Reliability via mocking
- 15:18Test data with API
- 18:30GUI validation in one line
- 23:14Debugging with traces
- 26:13Future: Playwright MCP
- 29:08Q&A
- 33:51Flakiness and reliability
- 34:54Visual and multi-platform tests
- 36:42Mocked API maintenance
- 38:54Who writes tests
- 40:20Playwright for API testing
- 41:25Secrets in traces
related talks
12mPlay It Right With Playwright
30mPlaywright: The Tool That Will Revolutionize End-to-End Testing
20mPlaywright or Selenium? The Modern Approach to UI Test Automation
41mTesting Web Applications with Playwright
35mState of end-to-end testing for modern web applications
45mDaniel Horn: Time to Test Your Web-Application Efficiently
39mTesting Web Applications with Playwright
30mTesting Web Applications with Playwright