Cypress vs Playwright vs Selenium: which framework to hand an agency
Updated
By Ronald Renaud, Analyst writing on QA vendors and test automation
Editorial ranking published by Ronald Renaud. Personal project of the publisher. No advertising, no vendor payments.
Pick the framework before you pick the agency, because the framework decides which teams can staff your project. Cypress fits a JavaScript or TypeScript web app where one team owns front-end tests and wants fast feedback in the browser. Playwright fits new suites that need WebKit, several tabs or origins in one test, or languages beyond JavaScript. Selenium fits organizations with a large existing suite in Java, C# or Python, or with a browser grid already in place. Most agencies in our ranking mention all three frameworks in their public materials, so the decision is yours to make.
Cypress vs Playwright vs Selenium at a glance
Every cell below was checked against official documentation on 2026-09-30.
| Aspect | Cypress | Playwright | Selenium | WebdriverIO |
|---|---|---|---|---|
| Test languages | JavaScript and TypeScript; test code runs in the browser (Cypress trade-offs) | JavaScript/TypeScript, Python, Java, .NET (Playwright languages) | Java, Python, C#, Ruby, JavaScript, Kotlin (Selenium docs) | Node.js, JavaScript/TypeScript (webdriver.io) |
| Browsers | Chrome family, Edge, Firefox; WebKit experimental; Electron deprecated (Cypress browsers) | Chromium, Firefox, WebKit, branded Chrome and Edge (Playwright browsers) | Chrome, Edge, Firefox, Safari, Internet Explorer (Selenium docs) | Any browser reachable over WebDriver or WebDriver BiDi (webdriver.io) |
| Architecture | Commands are queued and retried inside the browser (Cypress introduction); server work goes through cy.task or cy.request | Test runner in Node.js drives browsers from separate worker processes | W3C WebDriver drives the browser through a driver; Grid routes commands to remote browsers | Node.js runner over WebDriver and WebDriver BiDi |
| Parallel runs | Across CI machines, orchestrated by Cypress Cloud with the record flag (Cypress parallelization) | Built-in worker processes plus sharding across machines (Playwright parallelism) | Selenium Grid across machines (Selenium Grid) | Built into the runner through maxInstances; Grid or cloud providers (configuration) |
| Mobile | No native or mobile events support (Cypress trade-offs) | Emulated phones and tablets in the browser; no native apps (Playwright emulation) | Native apps through Appium, a separate project (Appium) | Real mobile devices through Appium (webdriver.io) |
| Component testing | Official mounting for React, Angular, Vue, Svelte (Cypress component testing) | Tests run against a story gallery page served by your dev server (Playwright components) | Not part of the project | React, Vue, Svelte and others (webdriver.io) |
| Licensing and paid services | App under MIT; Cloud has a free Starter tier and paid tiers (Cypress pricing) | Apache 2.0 (license) | Apache 2.0 (Selenium copyright) | MIT (repository) |
| Tabs, windows, iframes | One browser at a time; tabs via the @cypress/puppeteer plugin; cy.origin for other origins; same-origin iframes queried natively (Cypress trade-offs) | Several pages per browser context, popup events, frameLocator (pages, frames) | Window handles, new tab or window, frame switching (Selenium windows, frames) | switchWindow and switchFrame (switchWindow) |
| Network stubbing | cy.intercept spies on and stubs requests (cy.intercept) | page.route mocks and modifies requests (Playwright network) | Request and response handlers over WebDriver BiDi, enabled in options (Selenium BiDi network) | Built-in mocks; needs WebDriver BiDi (WebdriverIO mocks) |
The Cypress pricing page lists 500 test results per month on the free Starter tier. The Team tier is listed at $799 per year. A large suite that records results daily needs a paid Cloud plan or a self-hosted dashboard.
Which is faster, Playwright or Cypress, and why
We do not quote benchmark numbers here, because published results depend on the app, the network and the CI runner. The architecture explains most of the difference buyers see.
Cypress queues commands and retries each query until the element appears or a timeout passes, as its introduction describes. That removes most manual waits, and a single spec often feels quick in the interactive runner. Scaling is where the models diverge. The Cypress parallelization docs recommend spreading specs across several CI machines rather than running them in parallel on one.
Playwright runs test files in parallel worker processes by default, and each worker starts its own browser. A single CI machine with enough cores can therefore run a large suite in parallel without an external service, and sharding extends that across machines.
Selenium speed depends on where the browsers live: a remote Grid or cloud farm adds network latency to every command, in exchange for many browser versions from one suite.
Ask the vendor how many machines or workers its estimate assumes and who pays for them. The cost guide covers that line item.
Cypress vs Playwright for an agency engagement
Cypress is the stronger choice when the app is a single-origin web product in JavaScript or TypeScript, when front-end developers will read and extend the tests, and when component tests should share tooling with end-to-end tests. Its limits are documented: one browser at a time, restricted iframe handling, and cross-origin flows that need cy.origin.
Playwright is the stronger choice when the product includes login redirects across domains, payment popups, several tabs, or Safari coverage through WebKit. It also opens the hiring pool to Python, Java and .NET engineers, which matters if your back-end team will own the suite later.
Several ranked agencies publish a Cypress vs Playwright view. QA Madness recommends Playwright as the default for new web automation and positions Cypress for existing stacks, per its article on evaluating automation providers. Abstracta publishes guidance that switching from Cypress to Playwright makes sense when cross-browser limits or parallel scaling across machines become a constraint. TestDevLab publishes a blog post on choosing between the two and lists Selenium, Cypress and Playwright on its automation page.
Cypress vs Selenium: legacy suites and language fit
Selenium remains the default where the test code must live in Java or C#, where Internet Explorer or older Safari versions still matter, or where a Grid and years of page objects already exist. Cypress is usually easier to start with for a JavaScript team, because installation, runner, assertions and network stubbing come in one package.
Migration between them is a rewrite, not a translation, since Selenium test code often runs in a JVM or .NET process while Cypress test code runs in the browser. ThinkSys, the leader of our ranking, states on its Cypress service page that it does not recommend one-to-one translation of Selenium tests. The same vendor gives 8-16 weeks as a typical timeline for migrating a mature Selenium suite.
Cypress vs WebdriverIO and Cypress vs Jest
WebdriverIO is a Node.js framework like Cypress that speaks WebDriver and WebDriver BiDi like Selenium and reaches native mobile apps through Appium. If one JavaScript team must cover web and mobile, add it to your RFP.
Jest is a different category. Its configuration docs state that the default environment is Node.js, with jsdom available as a browser-like environment. Jest runs unit and integration tests without a real browser; Cypress drives a real one. Most teams use both: Jest for logic, Cypress for user flows. An agency proposal that replaces Jest unit tests with Cypress end-to-end tests will produce a slower, more expensive suite.
What the framework choice means for hiring an agency
Use this table when writing the brief.
| If your situation is | Framework to specify | What to check in the agency |
|---|---|---|
| JavaScript/TypeScript web app, front-end team will own tests | Cypress | Public Cypress cases, component testing experience, Cypress Cloud or self-hosted dashboard plan |
| New suite, several origins or tabs, Safari coverage needed | Playwright | Playwright cases, sharding setup in your CI, language match with your team |
| Large Java or C# suite, existing Grid | Selenium (keep) | Maintenance and flake-reduction record, Grid or cloud farm costs |
| Selenium suite to be replaced | Cypress or Playwright | Named migration cases, parallel-run plan during the switch, timeline |
| Web plus native mobile in one team | WebdriverIO or Selenium with Appium | Appium device coverage, real-device lab access |
Three contract points follow from the framework. First, repository ownership: the code should sit in your repository from week one, whichever tool is used; our how-to-choose guide lists the clauses. Second, paid services: Cypress Cloud seats, a Playwright or Selenium cloud grid, or device labs are separate costs that the quote should name. Third, skills continuity: a Cypress suite needs JavaScript maintainers, so a vendor staffing Java engineers onto it is a warning sign. The engagement models guide explains how dedicated teams and project work handle handover.
How ranked agencies position the three frameworks
The table below uses only public evidence collected for the ranking and scored under the methodology. Migration scores are the per-dimension values from the scoring table.
| Agency | Public framework evidence | Migration score |
|---|---|---|
| TestFort | Healthcare case: team began with Selenium IDE and switched to Cypress early in the project | 75 |
| Testrig Technologies | Fashion retail case: UI tests moved from Ghost Inspector to Cypress; separate article on a Selenium-to-Playwright migration with both suites running side by side in CI | 75 |
| DeviQA | Cypress service page offers an audit and transition strategy from Selenium or Playwright; QIMA case upgraded an outdated Cypress version | 50 |
| Codoid | Blog guide on migrating Cypress to Playwright; states it helps teams migrate to Playwright; no named migration case | 50 |
| QASource | States it migrated its own Selenium suite to Playwright with its QASIP tooling | 40 |
| QA Madness | Recommends Playwright for new web automation; legal software case selected Cypress with TypeScript | 0 |
| a1qa | Recent automation cases name Playwright or Selenium; blog covers Cypress component testing and Cypress Cloud parallel runs | 0 |
Vendors with public Cypress cases mostly describe moves into Cypress, while several general automation vendors now describe moves toward Playwright. The TestFort case records 450+ tests run nightly in Azure DevOps (vendor-published). The Testrig case ran Cypress specs in parallel in GitHub Actions, Jenkins and Docker with a Sorry-Cypress dashboard, a self-hosted alternative to Cypress Cloud.
If your scenario is a migration, start with the scenario table and filter by the vendors with migration evidence above.
Cypress to Playwright migration: what to ask before you pay for it
A migration is justified when a documented limit blocks a real test: a second tab, an iframe from another origin, WebKit coverage, or parallel cost. It is rarely justified by a benchmark alone.
Before approving one, ask the agency four questions:
- Which current tests fail or are skipped because of a Cypress limit, and how many are there?
- Will both suites run in CI during the switch, and for how long?
- Which custom commands, fixtures and intercepts need a Playwright equivalent, and who writes the mapping?
- What does the suite cost to run per month after the move, including any cloud grid?
Migrate the tests that hit a limit first, and keep the rest until the new suite proves stable.
FAQ
Can Cypress and Playwright be used together in one project?
Yes. They are separate runners with separate configs, so a repository can hold a Cypress folder and a Playwright folder, each with its own CI job. Cypress even depends on a Playwright package for one feature: its experimental WebKit support requires installing playwright-webkit, per the Cypress browser docs. Running both is common during a migration or when Playwright covers flows Cypress cannot, such as several tabs. Plan a date to consolidate the two sets of helpers and reports.
Which is faster, Playwright or Cypress?
It depends on how the suite is run, not on a single number. Playwright runs test files in parallel worker processes by default, each with its own browser, so one CI machine can run many files at once. Cypress retries commands inside the browser and spreads specs across several CI machines through Cypress Cloud orchestration. For a small suite the difference is minor; for a large one, compare total pipeline minutes and machine cost on your own app before you choose.
Should I use Cypress or Playwright for a new web app?
Choose Cypress if the app is a single-origin JavaScript or TypeScript product, front-end developers will own the tests, and component tests matter. Choose Playwright if you need WebKit coverage, several tabs or origins in one test, or test code in Python, Java or .NET. QA Madness, one of the ranked agencies, publicly recommends Playwright as the default for new web automation. Either way, write the choice into the agency brief so vendors quote the same scope.
Is Cypress better than Selenium?
For a JavaScript web team starting from zero, Cypress is usually quicker to set up, because runner, assertions and network stubbing ship together. Selenium covers more languages, including Java, C#, Ruby and Kotlin, more browsers including Safari, and native mobile apps through Appium. If your organization already runs a Selenium Grid with a large suite, rewriting it in Cypress costs weeks of work and needs a concrete reason.
When should I use Selenium over Cypress?
Use Selenium when the tests must be written in Java, C#, Python, Ruby or Kotlin, when you need Safari or older browsers, or when the same team also automates native mobile apps with Appium. Selenium also fits when a Grid and years of page objects already exist and still work. Cypress restricts tests to JavaScript and TypeScript and controls one browser at a time, so flows that need several windows are easier in Selenium or Playwright.
Should I migrate from Cypress to Playwright?
Only if a documented Cypress limit blocks tests you need: several tabs, cross-origin iframes, WebKit coverage or parallel cost. Count the affected tests first. If they are a small share, cover them in Playwright and keep the rest in Cypress. Abstracta publishes guidance that a switch makes sense when cross-browser limits or parallel scaling become a constraint. Ask any vendor proposing a migration for a named case, a period of running both suites, and a monthly run-cost estimate.
How long does a Selenium to Cypress migration take?
One public figure comes from the ranking leader, ThinkSys, which gives 8-16 weeks as a typical timeline for migrating a mature Selenium suite. Duration depends on the number of tests, the share that needs redesign rather than rewriting, and how much test data setup is shared. Selenium tests often run outside the browser while Cypress tests run inside it, so helpers usually need rework. Ask each agency for its own estimate against your suite and a named migration case.
What is the difference between Cypress and Jest?
Jest is a unit and integration test runner; its default environment is Node.js, with jsdom as a browser-like option. Cypress drives a real browser and tests user flows and mounted components. They solve different problems and most teams run both. A sound split keeps business logic in Jest, where tests take milliseconds, and keeps sign-up, checkout and similar journeys in Cypress. An agency quote should state which layer each test belongs to.
How does Cypress compare with WebdriverIO?
Both are Node.js frameworks written in JavaScript or TypeScript. Cypress runs its commands inside the browser and bundles its own runner, stubbing and dashboard service. WebdriverIO drives browsers over WebDriver and WebDriver BiDi, runs on Selenium Grid or cloud providers, and reaches real mobile devices through Appium. Pick WebdriverIO when one JavaScript team must cover web and native mobile; pick Cypress when the scope is a web app and fast local feedback matters most.
Does it matter which framework an agency prefers?
Yes, because the agency's preference shows up in who it staffs and what it proposes. An agency whose recent cases are all Playwright may push a migration you do not need. Check public cases by framework: TestFort and Testrig Technologies publish moves into Cypress, while Codoid and QASource publish material on moving toward Playwright. The ranking scores Cypress-specific evidence separately from general automation work, so use it to shortlist vendors whose record matches your chosen tool.