Selenium and Cypress to Playwright migration
We move a Selenium or Cypress suite to Playwright in stages, starting with the tests that guard your riskiest journeys. Old and new suites run side by side, and a migrated test only replaces the original once it has been shown to catch the same defects. Nothing is switched off on trust.
Should we migrate at all?
Not always. If your suite is stable, fast and trusted, migration may not pay for itself. It makes sense when tests are slow or flaky, when the old tool limits what you can test, or when maintaining it takes more time than the tests save. We assess before recommending anything.
How does the migration work?
We audit the current suite, group tests by risk, and migrate in stages. For each batch we write the Playwright version, run both versions side by side and compare results. When the new test passes and fails in the same situations as the old one, the old one is retired.
- Audit the current suite and group tests by risk
- Migrate one batch at a time
- Run old and new side by side
- Prove the new tests catch the same defects
- Retire the old tests
How do you prove the new tests catch the same defects?
We break the app on purpose in a controlled way, for example by removing a validation or changing a price, and confirm that both the old and the new test fail. A new test that stays green when the product is broken is rejected and rewritten.
What doesn’t carry over cleanly?
Custom commands, plugins and framework-specific tricks need to be rewritten, not translated. Cypress network stubbing and Selenium grid setups map to different Playwright features. Some old tests are better deleted than migrated, and we tell you which ones and why.
What does a Selenium or Cypress migration cost?
Each project is quoted on its scope, so there’s no price list. The main cost drivers are the size and quality of the current suite, how much custom tooling it uses, how long old and new suites run side by side, and the language you move to. Request a quote and we reply by email.
Frequently asked questions
Can we keep running Selenium during the migration?
Yes. Running both side by side is how the migration works. Nothing is switched off until its replacement is proven.
Will the migrated tests be faster?
Often, because Playwright runs tests in parallel and waits for pages to be ready. We measure the difference on your suite rather than promise it.
Do we have to change programming language?
No. Playwright supports TypeScript, JavaScript, Python, Java and .NET. We recommend what fits your team, and a language change is optional.
Ready to find out what is breaking?
Tell us what you’re shipping. We reply by email, and quote each project on its scope.