Cypress or Selenium to Playwright, without a big bang.
A strangler migration: the old suite stays green while Playwright grows beside it. The flakiest tests move first, because that is where the pain is.
Where to start
The audit measures the current suite and sizes the migration. The migration is scoped and priced from the audit report.
How it runs
- 01
Freeze, don't rewrite
No new Cypress or Selenium tests from day one. Bugs found in old tests get fixed in Playwright.
- 02
Flakiest 20% first
The audit ranks tests by retry count and duration. The worst ones are rewritten first, so CI gets faster in week one.
- 03
Parity before cut-over
Each migrated flow runs in both suites until Playwright has been green for a defined period. Then the old test is deleted.
- 04
CI cut-over
Sharded Playwright jobs replace the old stage. Reports, PR comments and artefacts move with them.
Questions
How long does a migration take?
One to three months for suites of a few hundred tests, depending on how much page-object logic must be rewritten. The audit gives a number.
Do our engineers need to learn Playwright?
Yes, and they will by pairing on the migrated flows. The handover includes a written guide and a review of their first pull requests.
What about Selenium in Java or C#?
Same approach. The Playwright suite is written in TypeScript unless your team is standardised on another language Playwright supports.
Can we keep Cypress for some tests?
You can, but two runners mean two sets of flakiness. We recommend a full cut-over with a defined end date.
Book a 30-minute discovery call.
Tell us about the suite and the CI. We say whether an audit makes sense and what it would cover.