Migrate Cypress to Playwright without rewriting everything.

The Test Adapter in Nexus StudioQA converts Cypress and WebdriverIO tests to Playwright by rule, in beta. You see the diff, every assertion is kept, and each converted test is rehearsed before it counts. What no rule can convert is listed, not hidden.

By the Nexus StudioQA team, Verdict System LLC.

Last updated: .

How a conversion works

Nothing is rewritten by hand, and nothing is converted in silence.

  • Rules first, AI only for the rest

    The conversion is a set of fixed rules, not a prompt. An optional AI handles only the parts no rule covers, and its code faces the same strict Vet check as any AI-written test. If you use it, the engine's verdict on the first answer goes back to the writer once, and the second answer replaces the first only if it is not worse.

  • You see the diff

    The review screen shows the original and the converted test side by side, with the assertion count before and after.

  • Every assertion is kept

    Assertions, conditions, loops and waits stay as they were. If a converted test would lose an assertion, the import is blocked unless you accept it, line by line.

  • Each test is rehearsed before it counts

    Converted tests start in a sandbox that writes no evidence and no history. A test leaves it after three clean rehearsals, each on a different browser, so one that only passes on Chromium falls over on the second.

  • What does not convert stays visible

    Project-specific commands, visual-testing plugins and cy.task stay as listed leftovers with their original lines, for the optional AI or for you. Measured once on two public Cypress suites, about half the files of one converted by rule with nothing left over, and none of the other, whose tests lean on project code. On a large project, expect some files to need that last step.

Source to what happens today

SourceWhat happens todayNotes
CypressConverted to Playwright (beta)Diff shown, assertions kept, each test rehearsed. cy.task and visual-testing plugins stay as leftovers.
WebdriverIOConverted to Playwright (beta)Same review: diff, assertion count, rehearsal.
Selenium in JavaScript, TypeScript or PythonAdapted and importedRewritten by rule into the Studio's fixture. The test stays Selenium.
Selenium IDE (.side)Read, and written as Playwright tests in JavaScript or PythonSee Selenium and Selenium IDE.
PlaywrightAdapted and importedBrowser launch and setup move into the Studio's fixture; assertions stay.
Robot FrameworkExperimentalNot part of the beta.
Java and C#Not converted todayPlanned next on the roadmap: convert them, not only read them.
Katalon, TestRail, Gherkin, Appium and PostmanNot available todayOn the roadmap, under Later. No dates.

Selenium and Selenium IDE

Selenium tests are adapted and Selenium IDE projects are read. Neither needs a rewrite from scratch.

  • Selenium code

    Tests written with Selenium in JavaScript, TypeScript or Python under mocha, jest, pytest or unittest are adapted by rule. They stay Selenium tests, and your team can keep reading and editing them as standard files.

  • Selenium IDE projects

    A .side file is plain JSON, and the adapter reads it as it is. Each locator comes from the targets the IDE recorded for that step; none is invented. Control flow (if, while, times, do, forEach) and any command with no rule stay out of the file as leftovers, with their original line.

What is not here yet

The full list, with its status, is on the roadmap.

  • Migration proof

    A report that shows converted tests behave like the originals before you retire them. Planned next; today the rehearsal is your check.

  • Java and C# converted, more sources

    Java and C# conversion is planned next. Katalon, Gherkin, Appium, Postman and TestRail are on the roadmap, later. It is a direction, not a commitment: no dates, and an item can be dropped.

Rehearse your first converted test.

Try every feature free, on your own machines. No card needed.