SoftwareTestPilot
Automation TestingPublished: 12 min read

Cypress vs Playwright vs Selenium — 2026 Decision Matrix

Not another feature list. A 12-criteria decision matrix built from 4 real production migrations, with hard numbers on speed, flake rate, CI cost, and hiring pool.

Avinash K
Founder & QA Engineer at SoftwareTestPilot
Share:XLinkedInWhatsApp
Decision matrix comparing Cypress, Playwright, and Selenium.
Decision matrix comparing Cypress, Playwright, and Selenium.

Last updated 2026-07-20 · 12 min read · By Avinash K

Framework comparison posts are usually vendor bingo. This one is different — it is built from 4 real migrations we tracked over 2024-2026, including one team that moved from Cypress to Playwright and one that moved off Playwright back to Selenium 4. Numbers, not opinions.

Key takeaways

  • The 12 decision criteria that actually matter.
  • Real flake rates, CI costs, and time-to-green.
  • When Selenium 4 still wins in 2026.
  • The migration decision tree.

1. The 12-criteria matrix

CriterionCypressPlaywrightSelenium 4
Cross-browserChromium, Firefox, Edge, WebKitChromium, Firefox, WebKitAll + real Safari, IE mode
Parallel execPaid (Dashboard) or OSS shardingNative, freeGrid required
Multi-tab / multi-originLimitedNativeNative
iFrame handlingWorkaroundsNative (frameLocator)Native
Language supportJS/TS onlyJS/TS, Python, .NET, JavaEvery major lang
Test speed (median)FastFastestSlowest (RPC overhead)
Flake rate (our data)1.8%0.6%2.4%
CI cost / 1k tests$14$8$22
Hiring poolMediumGrowing fastLargest
Mobile webLimitedEmulation onlyAppium bridge
Component testingStrongStrongNot supported
Ecosystem age201720202004

2. When each one still wins

  • Cypress — small SPA teams, JS/TS shop, component-first, willing to pay for Dashboard parallelism.
  • Playwright — greenfield, cross-browser required, cost-sensitive CI, polyglot team.
  • Selenium 4 — enterprise multi-language shops, real Safari / IE mode, existing grid infra, huge hiring pool.

3. Decision tree

Answer these in order: (1) Do you need real Safari or IE? → Selenium. (2) Is your team JS-only and building components? → Cypress. (3) Everything else → Playwright. That is not a joke — it is the outcome of 4 migration calls.

4. Migration cost

Cypress → Playwright: ~2 weeks per 100 tests (selectors translate 1:1 in most cases). Selenium → Playwright: ~3 weeks per 100 tests (waits and fixtures need rewrite). See our Playwright locators guide, Selenium locators cheat sheet, and fixtures deep dive for the concrete translation patterns.

Frequently asked questions

1.What about WebdriverIO?
Excellent framework, especially with Appium for mobile, but the ecosystem centre of gravity has moved to Playwright for web-first teams.
2.Does Cypress support cross-origin now?
Yes since v12 (cy.origin), but the ergonomics still lag behind Playwright's context.newPage().
3.Where did the flake numbers come from?
Aggregated across 4 client migrations we tracked in 2024-2026. Each ran the same 200-test suite for 30 days on identical CI infra.
4.Should I rewrite an existing 500-test Selenium suite?
No. Migrate only when you are also adding significant coverage or the framework is blocking a business need (parallelism, WebKit, cost).