About 24; min
Cypress, Playwright, and Selenium have been competing for the end-to-end testing crown. Cypress dominated the 2020s with developer-friendly UX. Playwright arrived from Microsoft and caught up fast. Selenium is the 20-year veteran that refuses to die. All three are open-source and free — so the real cost is developer time and CI infrastructure.
Quick Pricing Comparison
| Tool | Open-Source | Cloud Service | CI Cost Impact |
|---|---|---|---|
| Cypress | Free (MIT) | Cypress Cloud: $75/mo (500 test results) | Medium (single browser per run) |
| Playwright | Free (Apache 2.0) | No official cloud | Lowest (parallel by default) |
| Selenium | Free (Apache 2.0) | BrowserStack/Sauce Labs: $29–$299/mo | Highest (slower execution) |
The tools themselves are free. The costs come from: CI/CD minutes consumed by test runs, cloud dashboard services for test management, and developer time writing and maintaining tests. Playwright’s faster execution saves the most CI minutes — which translates to real money at scale.
Cypress: Developer Experience First
Cypress’s open-source test runner is free and covers everything you need to write and run tests locally. Cypress Cloud ($75–$300/month) adds parallelization (split tests across CI machines for faster runs), flaky test detection, and analytics dashboards.
Cypress’s Strengths
- Time-travel debugging: Step through each test command and see exactly what the browser showed at each step. No other tool makes test debugging this visual
- Automatic waiting: Cypress automatically waits for elements to appear, animations to finish, and network requests to complete. No manual waitFor() calls or sleep() hacks
- Component testing: Test individual React, Vue, Angular, or Svelte components in isolation. Useful for design system testing alongside E2E
- Developer UX: The test runner GUI, error messages, and documentation are the most beginner-friendly. New developers write their first test in minutes
Cypress’s Limitations
- Single browser tab: Cypress runs inside the browser, so multi-tab and multi-window testing isn’t possible. Testing OAuth flows that open popup windows requires workarounds
- No native mobile: No iOS Safari or Android browser testing. Desktop Chrome, Firefox, and Edge only
- Slower CI execution: Cypress runs tests serially within a single browser instance. Parallelization requires Cypress Cloud (paid) or custom CI configuration
- JavaScript only: Tests must be written in JavaScript/TypeScript. Playwright supports Python, Java, and C# too
Playwright: The Speed Champion
Playwright has no paid cloud service — everything is free and open-source. Parallelization, browser downloads, trace viewing, and code generation are all included at $0.
Playwright’s Strengths
- Multi-browser including Safari: Test on Chrome, Firefox, AND Safari (WebKit) from the same codebase. Cypress can’t test Safari at all. For teams with significant Safari/iOS traffic, this alone justifies Playwright
- Built-in parallelization: Run tests in parallel across multiple workers without any paid service. Cypress requires Cloud ($75/month) for parallelization. Playwright does it for free
- Multi-tab and multi-origin: Test OAuth flows, popup windows, and cross-origin scenarios natively. Cypress can’t handle these
- Speed: Playwright executes 2–3x faster than Cypress in most benchmarks. A 10-minute Cypress suite runs in 3–5 minutes on Playwright. At scale, this saves hundreds of CI minutes per month
- Multi-language: Write tests in JavaScript, TypeScript, Python, Java, or C#. Backend teams don’t need JavaScript knowledge
- Codegen: Record browser actions and Playwright generates test code automatically. The fastest way to create initial test scaffolds
- Tracing: Built-in trace viewer shows DOM snapshots, network requests, and console logs at each step — similar to Cypress’s time-travel but without a paid dashboard
Playwright’s Limitations
- No component testing: Playwright focuses on E2E testing. Component testing exists experimentally but isn’t as mature as Cypress’s
- Steeper learning curve: More configuration options and less hand-holding than Cypress. The documentation is thorough but less beginner-friendly
- No official dashboard: Playwright has no paid cloud dashboard for test analytics, flaky test detection, or team reporting. You build your own or use third-party tools (Allure, ReportPortal)
Selenium: The Legacy Standard
Selenium is free and supports every browser, every language, and every platform. It’s the W3C standard for browser automation. But its architecture (external driver process communicating over HTTP) makes it slower and more brittle than Cypress or Playwright’s direct browser control.
When Selenium Still Makes Sense
- Java/C# shops: If your team writes Java or C# and doesn’t know JavaScript, Selenium’s Java and C# bindings are the most mature (Playwright’s are close behind)
- Legacy test suites: Millions of Selenium tests exist in production. Rewriting them in Playwright takes months. Maintaining existing Selenium suites while gradually migrating makes practical sense
- Selenium Grid: Distribute tests across hundreds of browsers/OS combinations simultaneously. Useful for cross-browser compatibility testing at enterprise scale
- BrowserStack/Sauce Labs: Cloud browser farms ($29–$299/month) run your Selenium tests on real devices (iPhones, Samsung phones, IE11). Playwright and Cypress cloud device support is more limited
Selenium’s Downsides (Why Teams Migrate Away)
- Flaky tests: Selenium’s architecture creates race conditions. Elements not found, stale element references, and timing issues are daily frustrations. Playwright and Cypress have auto-waiting that eliminates most flakiness
- No auto-waiting: You manually add waits (explicit, implicit, fluent) to handle dynamic content. Miss a wait and your test fails intermittently
- Slow execution: HTTP-based driver communication adds latency. A Selenium suite takes 3–5x longer than Playwright for the same tests
- Complex setup: Install the browser driver, configure the driver path, manage driver versions, set up Grid for parallelization. Playwright downloads browsers automatically with one command
CI Cost Comparison
The hidden cost of E2E testing is CI minutes. Faster tests = fewer CI minutes = lower bills.
| Suite Size | Cypress (serial) | Playwright (parallel) | Selenium |
|---|---|---|---|
| 50 tests | 8 min | 3 min | 15 min |
| 200 tests | 30 min | 8 min | 55 min |
| 500 tests | 75 min | 15 min | 130 min |
At 500 tests run 20 times per day (typical for an active team), monthly CI minutes:
| Tool | Minutes/Day | Minutes/Month | GitHub Actions Cost (~$0.008/min) |
|---|---|---|---|
| Cypress | 1,500 | 45,000 | $360 |
| Playwright | 300 | 9,000 | $72 |
| Selenium | 2,600 | 78,000 | $624 |
Playwright saves $288/month vs Cypress and $552/month vs Selenium in CI costs alone — for the same tests producing the same coverage. Over a year, Playwright’s speed advantage saves $3,456–$6,624 in CI bills.
Feature Comparison
| Feature | Cypress | Playwright | Selenium |
|---|---|---|---|
| Browsers | Chrome, Firefox, Edge | Chrome, Firefox, Safari, mobile | All browsers |
| Languages | JavaScript/TypeScript | JS, TS, Python, Java, C# | Java, Python, C#, Ruby, JS |
| Auto-waiting | Yes | Yes | No (manual waits) |
| Parallel execution | Cloud only ($75/mo) | Built-in (free) | Grid (free, complex setup) |
| Multi-tab/multi-origin | No | Yes | Yes |
| Component testing | Yes (mature) | Experimental | No |
| Mobile testing | No | Mobile emulation | Real devices (via BrowserStack) |
| API testing | Limited | Built-in | No |
| Code generation | Cypress Studio (basic) | Codegen (best) | Selenium IDE |
| Dashboard/analytics | Cypress Cloud (paid) | No official (use Allure) | No official |
| Execution speed | Medium | Fastest | Slowest |
| Flaky test handling | Cloud detection ($75/mo) | Retry logic (built-in) | Manual |
Who Should Pick What
Pick Cypress If:
- Your team is new to E2E testing and values the best learning experience
- Component testing (React/Vue/Svelte) is as important as E2E testing
- The visual test runner and time-travel debugging are worth the slower execution
- You’re willing to pay for Cypress Cloud ($75/month) for parallelization and analytics
Pick Playwright If:
- Execution speed and CI cost savings are priorities
- Safari/WebKit testing is required (Cypress can’t test Safari)
- Multi-tab, multi-origin, or OAuth popup testing is part of your test suite
- You want everything free — parallelization, tracing, and codegen at $0
- Your team writes Python, Java, or C# (not just JavaScript)
- You’re starting a new test suite from scratch (no legacy to maintain)
Pick Selenium If:
- You have an existing Selenium suite and migration isn’t worth the effort yet
- Real device testing via BrowserStack/Sauce Labs is required for mobile QA
- Your team’s primary language is Java or C# with deep Selenium expertise
- Cross-browser compatibility across legacy browsers (IE11, older Safari) is needed
Best for new projects: Playwright — fastest execution, free parallelization, Safari support, and multi-language. The default choice for any team starting E2E testing in 2026.
Best developer experience: Cypress — time-travel debugging, component testing, and the most beginner-friendly docs. Worth the speed trade-off for teams that value DX.
Best for legacy: Selenium — if you have 10,000 existing Selenium tests, maintain them. Migrate to Playwright gradually, not all at once.
CI cost winner: Playwright — 2–5x faster execution saves $3,000–$6,000/year in CI bills for medium-size test suites.
FAQ
Can I migrate from Cypress to Playwright?
Yes. The test structure is similar (describe/it blocks, locators, assertions). Microsoft provides a migration guide. Expect 1–2 days per 100 tests, mostly changing API calls. The hardest part: replacing Cypress-specific commands (cy.intercept, cy.task) with Playwright equivalents.
Do I need a cloud testing service?
For Playwright: No — parallelization and tracing are free. For Cypress: Yes, if you want parallelization ($75/month). For Selenium: Recommended for cross-browser/device testing (BrowserStack $29+/month). You can always self-manage CI runners instead of cloud services.
Which is best for API testing?
Playwright includes a native API testing module (request fixtures). Cypress can make API calls but it’s not a core feature. For dedicated API testing, use Postman, Bruno, or a separate API testing framework alongside your E2E tool.
Should I use E2E tests or unit tests?
Both. The testing pyramid: many unit tests (fast, cheap), some integration tests, few E2E tests (slow, expensive). E2E tests cover critical user journeys (signup, checkout, core workflows). Unit tests cover individual functions and components. Don’t replace one with the other.
