128 / 139 · 13 Browser Automation with Playwright · Migration and Comparison← prev⊞ allnext →☰ Read as one page
15.3When to Choose What
Choose Playwright When
- Starting a new project with no existing test suite
- Team uses TypeScript, Python, Java, or C#
- Need cross-browser testing (including WebKit/Safari engine)
- Need network mocking, multi-tab, or advanced browser control
- Want built-in test infrastructure (runner, reporter, traces)
Keep Selenium When
- Large existing Selenium suite with years of investment
- Team uses Ruby, Go, or other languages Playwright does not support
- Need real Safari testing (not WebKit approximation)
- Organization mandates Selenium or uses Selenium Grid infrastructure
- Integrating with Appium for mobile native testing
Choose Cypress When
- Team is exclusively JavaScript/TypeScript
- Testing a single-page application
- Developer experience and fast feedback loop are the priority
- Do not need multi-tab or multi-origin testing
- In-runner AI authoring appeals to the team — Cypress v15's
cy.prompt()and Cypress Studio lower the writing barrier