open-testing-convert-cypress

Convert Cypress tests to and from Playwright, Selenium, and other frameworks.

13|1|Updated Mar 16, 2026
One-click install
npx skills add https://github.com/AgenticTesting/OpenTestingAI --skill open-testing-convert-cypress
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: open-testing-convert-cypress
Source: https://github.com/AgenticTesting/OpenTestingAI/tree/main/.opentesting-convert/skills/open-testing-convert-cypress
Command: npx skills add https://github.com/AgenticTesting/OpenTestingAI --skill open-testing-convert-cypress

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Cypress tests are locked to a single framework; this skill enables migrating and round-tripping tests between Cypress and other engines (Eggplant, OpenTest.AI, Testers.AI, Selenium, and Playwright) to maximize reuse and validation.

Core Features & Use Cases

  • Converts Cypress tests into canonical intents for downstream targets and translates intents back into Cypress-ready code.
  • Supports Cypress 10+ JS/TS syntax: cy.visit, cy.get, .should, cy.intercept, and common plugins; defers orchestration to the master skill.
  • Use cases: migrate a Cypress suite to Playwright or Selenium; translate a single spec into another framework; verify round-trips by translating back to Cypress.

Quick Start

Provide a Cypress project directory and choose a target framework to begin the conversion.

Frequently Asked Questions about open-testing-convert-cypress

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I convert Cypress tests to Playwright or Selenium?

You can convert Cypress tests to Playwright or Selenium by providing a Cypress project directory and selecting a target framework. The skill translates Cypress JS/TS syntax into canonical intents and generates the target code.

What Cypress commands and syntax are supported for test conversion?

The test conversion supports Cypress 10+ JS/TS syntax including cy.visit, cy.get, .should, cy.intercept, and common plugins. These elements are mapped to canonical intents for consistent translations across target frameworks.

Can I round-trip a translated test back to Cypress to verify accuracy?

Yes, you can verify round-trips by translating a spec to another framework and back to Cypress. The skill loads per-target primers and reference material to drive consistent, round-trip translations between Cypress and other engines.

Does this Cypress test conversion tool support Eggplant and OpenTest.AI?

Yes, the tool supports converting Cypress tests to and from Eggplant and OpenTest.AI. It also handles Testers.AI Recorder, Testers.AI Dynamic, Selenium, and Playwright, maximizing test reuse and validation across engines.

What is the best way to migrate a full Cypress suite to another framework?

The best way to migrate a Cypress suite is to provide the full Cypress project directory and choose a target framework. The skill handles the JS/TS syntax translation and defers orchestration to the master skill for broader suite management.