2.6 1-Click Migration from Cypress, Selenium & Playwright

How to ingest existing test codebases into CertiQA to gain visual triage, self-healing, and unified reporting.

Two Migration Paths, Chosen Automatically

Rewriting an existing Cypress or Playwright suite by hand just to get it into CertiQA is exactly the kind of throwaway work a migration tool exists to avoid. Upload a script and CertiQA auto-detects its format – filename convention, cy. idiom density, @playwright/test / page. idioms, or a Postman Collection v2.1 JSON shape – and routes it down one of two paths. Playwright, Cypress, and Postman Collection exports go through real, deterministic static parsers – hand-rolled source analysis, not an LLM guessing at intent – so the same input produces the same output every time. Selenium/Java and Protractor scripts don’t have a static parser yet, so they go through LLM-based translation instead – still fully supported, just a different, slightly less predictable mechanism underneath.

Reading the Fidelity Grade

Every migrated suite comes back with a fidelity grade – EXCELLENT, GOOD, or NEEDS_REVIEW – describing how much of the source the static parser could confidently recognize, plus a per-line import warning for anything it couldn’t: dynamic control flow, a custom command, a page-object method call, or any construct outside what the parser understands. A NEEDS_REVIEW grade automatically falls back to LLM translation for that script rather than handing you a half-parsed suite silently.

Migrating a Suite

• 1. In Test Suites, click “Import Script.”
• 2. Upload one or more source files – .spec.ts (Playwright), .cy.js (Cypress), a Postman Collection export, or Selenium Java/Python – format detection needs no manual selection.
• 3. Review the returned suite and its fidelity grade before saving; treat a NEEDS_REVIEW case the way you’d treat any AI-generated draft – worth a read before it goes into CI.

What Transfers, and What Doesn’t

• Selectors carried over from the original script keep working, but they don’t automatically gain locator candidates or a confidence score the way a CertiMind-generated step does – consider running the Triage Drawer once against a freshly migrated suite to see what self-healing would propose.
• A custom command or page-object helper in the source script has no CertiQA equivalent to parse into – expect an import warning on those lines even from an otherwise EXCELLENT-graded migration.