Cypress to Playwright migration, without losing a release
We convert your Cypress tests to Playwright, check every converted file by hand, and run both suites side by side until Playwright has earned the job of gating your releases. Cypress is only removed after five green production deployments.
What you get at the end
- A Playwright suite in TypeScriptIn your repository, from the first commit
- Playwright as your CI gateGitHub Actions, GitLab CI or your existing CI
- A conversion reportEvery file: converted, fixed or rewritten
- A half-day workshopSo your developers can write the next test
What a migration covers
A line-by-line translation is the easy part. These are the parts that decide whether the new suite can be trusted.
Every spec file
All your .cy.js and .cy.ts files, converted to Playwright TypeScript with modern locators.
Custom commands
cy.login() and friends become helper functions or Playwright fixtures, documented for your team.
Authentication
Login moves out of before() hooks into a global setup that saves the session once.
Network mocks
cy.intercept() becomes page.route() or a recorded HAR file, whichever is cleaner for that API.
Waits and timeouts
Fixed cy.wait() calls are replaced with assertions that wait for the real condition.
Plugins and tabs
We find a Playwright equivalent for each plugin you rely on, and drop old multi-origin workarounds.
Four phases, and Cypress stays until the end
A typical plan for 100 to 300 tests runs six to eight weeks. Your proposal gives the plan for your suite.
Convert
A conversion script with strict rules turns every file into Playwright, in a separate folder. Nothing is deleted.
Review
Engineers run each converted test, sort the failures and fix custom commands, fixtures and login.
Run in parallel
Both suites run on the same commits. We compare pass rates, run times and flaky tests.
Cut over
Playwright becomes the CI gate. Cypress stays as a fallback and goes after five green production deployments.
A script does the typing. Engineers do the checking.
Conversion tooling gets most files close. The rest needs someone who knows why a test exists, which is where our engineers spend their time.
- Engineers who did not write your code, so they question it
- Every converted file reviewed before it counts
- NDA and DPA signed before anyone sees your repository
When the migration counts as finished
We agree these gates with you at the start, and the final report shows each one.
95% or more passing
On the converted suite, with no test that passes in Cypress and fails in Playwright.
No slower, no flakier
Each test run ten times. Run time and flake rate must be at or below Cypress.
Your team can carry on
Your developers write a new Playwright test in the workshop, not after we leave.
Writing new tests afterwards? Flows, our recorder, exports a recorded test as a Playwright script (JS or TS), a Cypress spec, or a Selenium script (JS).
What a migration costs
A migration is a fixed piece of work. After a call and a look at your suite, the proposal gives one fixed price, based on the number of tests and how many custom commands, mocks and plugins they use.
If you keep us on for ongoing test automation afterwards, our usual monthly terms apply, including the trial.
Want to read how it works first? Our guide on how to migrate Cypress to Playwright walks through each step.
Cypress to Playwright migration: common questions
How long does a Cypress to Playwright migration take?
A typical plan for 100 to 300 tests runs six to eight weeks, about half of it on the parallel run and the cutover. Your proposal gives the plan for your suite.
Can AI convert Cypress tests to Playwright?
It gets most files close, fast. Custom commands, heavy network mocks and plugins still need an engineer, so we review every converted file before it counts.
Do we have to stop releasing during the move?
No. Cypress keeps gating your releases until the Playwright suite has matched it on the same commits, and it stays as a fallback after the cutover.
Who owns the new tests?
You do. The Playwright suite, its config and the CI workflow live in your repository from the first commit.
TypeScript or JavaScript?
We recommend TypeScript, and that is our default. If your team works in JavaScript, we convert to JavaScript.
How is the price set?
Our rate is €20 to €45 per hour. A migration is quoted as one fixed price in the proposal, based on the size and shape of your suite.
Tell us about your Cypress suite
How many tests, which plugins, what breaks. We reply within one business day and send a proposal within 2 business days of the call.