Daniel Horn: Time to Test Your Web-Application Efficiently
summary
Compares Selenium, Cypress and Playwright on a webshop buy flow using 100 runs per combination in containerized CI to fix versions; measures runtime, browser ramp-up (~3s) and reliability. Finds Node APIs faster than Java, Cypress runs slower than Playwright, and Playwright Java incurs a big 60s startup penalty for Playwright Java because it spawns Node, so Playwright JS finishes ~30 minutes vs Selenium Java ~90 minutes across the full job build-heavy benchmark. Highlights Playwright’s trace feature captures DOM and network for debugging.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 3:01Compare open source test tools
- 7:04Methodology and tool selection
- 12:28Selenium vs Cypress vs Playwright
- 14:36Key findings and recommendations
- 17:30Playwright Java startup time
- 20:45Build process impact on tests
- 22:09Browser interaction and tabs
- 27:06Screenshots and video reporting
- 32:09Use cases and strengths
- 37:10Tool selection criteria
- 38:40Final recommendations
- 40:26Q&A
related talks
20mPlaywright or Selenium? The Modern Approach to UI Test Automation
39mTesting Web Applications with Playwright
30mPlaywright: The Tool That Will Revolutionize End-to-End Testing
51mCypress, Playwright or Selenium: choosing the right testing tool
46mTest Automation with Selenium, Cypress, and Playwright
16mE2E Test Automation Framework Selection | Comparing with Pros & Cons
18mPlaywright: Revolutionizing Cross-Browser Compatibility
21mCypress, Playwright or Selenium: choosing the right testing tool