Run any Skill in Manus with one click

open-testing-convert-cypress

Stars13

Forks1

UpdatedApril 20, 2026 at 11:58

Convert Cypress tests to and from Eggplant (SenseTalk), OpenTest.AI, Testers.AI Recorder, Testers.AI Dynamic, Selenium, and Playwright. Handles Cypress JavaScript/TypeScript (`cy.visit`, `cy.get`, `.should`, `.click`, `.type`, custom commands, intercepts) and common add-ons (Cypress Testing Library, cypress-real-events, @cypress/grep). Use whenever the user wants to migrate a Cypress suite, translate a single spec, or round-trip Cypress through another framework. MANDATORY TRIGGERS — "convert Cypress", "Cypress to Playwright", "Cypress to Selenium", "Cypress to Eggplant", "migrate Cypress", "translate cypress test", "port Cypress", "Cypress → OpenTest.AI", "Cypress to Testers.AI", or any mention of Cypress alongside any of the supported targets.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

AgenticTesting

AgenticTesting/OpenTestingAI

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software Quality Assurance Analysts and TestersComputer and Mathematical Occupations·SOC 15-1253

File Explorer

4 files

SKILL.md

readonly

More from this repository

same repository

open-testing-coverage

AgenticTesting/OpenTestingAI

Test coverage analysis, gap detection, coverage reporting, and coverage optimization using the COVERED agent pipeline. Use this skill whenever the user mentions test coverage, coverage analysis, coverage gaps, traceability matrix, coverage heat map, coverage dashboard, coverage metrics, coverage trends, test intensity, risk-based coverage, requirement coverage, code coverage mapping, or wants to know if their testing is sufficient. Also trigger when users ask about uncovered requirements, orphaned tests, coverage regression, or coverage targets. MANDATORY TRIGGERS: coverage, traceability, gap analysis, RTM, heat map, coverage dashboard, coverage trend, test intensity evaluation.

2026-05-1413

open-testing-create

AgenticTesting/OpenTestingAI

Generate concrete test cases, test data, and test scripts from a test design technique and context. Applies 106 test design techniques (boundary value analysis, equivalence partitioning, decision tables, state transitions, pairwise, combinatorial, etc.) to enumerate test conditions and author realistic test cases with inputs, expected results, and traceability. Use this skill whenever the user needs to: create test cases from a technique, apply a testing method to requirements, generate test data, design test scenarios, or populate test scripts. Triggers include: 'test cases', 'create tests', 'test design', 'apply [technique name]', 'generate test data', 'test scenarios', or any technique name (BVA, EP, combinatorial, etc.).technique name (BVA, EP, combinatorial, etc.).

2026-05-1413

open-testing-design

AgenticTesting/OpenTestingAI

Generate comprehensive test strategies, quality engineering approaches, risk analysis, and optimal technique selection. Use this when you need to develop test strategies, perform quality risk analysis, select test design techniques, assess testability, estimate test effort, define governance structures, or establish test exit criteria and coverage targets.

2026-05-1413

open-testing-management

AgenticTesting/OpenTestingAI

Test management, defect management, process evaluation, and maturity assessment using the MANAGES agent pipeline. Use this skill whenever the user mentions test management, defect management, process improvement, TMMi, maturity assessment, ARCI matrix, quality policy, test policy, process evaluation, defect lifecycle, triage, test process, roles and responsibilities, QAM, QPM, GTA, generic test agreements, process maturity, test improvement, or wants to evaluate and improve their testing practices. Also trigger for defect tracking, anomaly management, process compliance, test governance, or organizational testing capability. MANDATORY TRIGGERS: test management, defect management, TMMi, maturity, ARCI, process improvement, quality policy, defect lifecycle, process evaluation, test governance.

2026-05-1413

open-testing-plan

AgenticTesting/OpenTestingAI

Generate comprehensive test plans, schedules, resource allocation, environment setup, and test data strategies. Use this when you need to develop master test plans, level-specific test plans, allocate resources and environments, plan non-functional testing, define end-to-end testing chains, or establish test data management strategies.

2026-05-1413

open-testing-reporting

AgenticTesting/OpenTestingAI

Test reporting, progress dashboards, release advice, and final test reports using the REPORTS agent pipeline. Use this skill whenever the user mentions test report, progress report, test dashboard, release advice, go/no-go decision, test metrics, defect trends, test execution summary, quality assessment, final test report, lessons learned, RAG status, or wants to generate any kind of testing status or quality report. Also trigger for executive summaries, sprint test reports, release readiness, or stakeholder communication about testing. MANDATORY TRIGGERS: test report, progress, dashboard, release advice, go/no-go, test metrics, defect trend, RAG status, quality report, test summary

2026-05-1413

name	open-testing-convert-cypress
description	Convert Cypress tests to and from Eggplant (SenseTalk), OpenTest.AI, Testers.AI Recorder, Testers.AI Dynamic, Selenium, and Playwright. Handles Cypress JavaScript/TypeScript (`cy.visit`, `cy.get`, `.should`, `.click`, `.type`, custom commands, intercepts) and common add-ons (Cypress Testing Library, cypress-real-events, @cypress/grep). Use whenever the user wants to migrate a Cypress suite, translate a single spec, or round-trip Cypress through another framework. MANDATORY TRIGGERS — "convert Cypress", "Cypress to Playwright", "Cypress to Selenium", "Cypress to Eggplant", "migrate Cypress", "translate cypress test", "port Cypress", "Cypress → OpenTest.AI", "Cypress to Testers.AI", or any mention of Cypress alongside any of the supported targets.
license	MIT
metadata	{"family":"open-testing-convert","source":"cypress","orchestrator":"open-testing-convert","targets":["eggplant","opentestai","testersai-recorder","testersai-dynamic","selenium","playwright"]}

Convert — Cypress

Converts tests from Cypress to any supported target, and to Cypress from another framework. Defers orchestration, target semantics, and cross-framework rules to the open-testing-convert master skill.

When to use

Trigger when:

The user references a Cypress project, spec file, or snippet and asks to migrate or translate it.
The user asks to convert to Cypress from Selenium, Playwright, a Testers.AI recording, or a natural-language format (OpenTest.AI, Testers.AI Dynamic).
The user uploads a .cy.js, .cy.ts, or legacy integration/**/*.spec.js file containing cy.visit, cy.get, describe(...) with cy. calls, cypress.config.ts / cypress.config.js, or cypress/support/e2e.{js,ts} / cypress/support/commands.{js,ts}.
cypress.json (legacy) or cypress.config.* is present.

How to use

Read the master orchestrator first. Open ../open-testing-convert/SKILL.md and follow its step order (detect source → detect target → resolve language → delegate to this skill → read target primer → validate output).
Confirm target and language. The master's language-policy.md governs language choice (default: preserve source language unless the user requests otherwise). Cypress is JS/TS only; for non-JS targets the language flips.
Read the relevant target primer:
- ../open-testing-convert/reference/targets/eggplant.md
- ../open-testing-convert/reference/targets/opentestai.md
- ../open-testing-convert/reference/targets/testersai-recorder.md
- ../open-testing-convert/reference/targets/testersai-dynamic.md
- For Selenium reverse: consult ../open-testing-convert-selenium/reference/source-profile.md.
- For Playwright reverse: consult ../open-testing-convert-playwright/reference/source-profile.md.
Read this skill's reference files:
- reference/source-profile.md — what Cypress tests look like.
- reference/extraction.md — how to extract canonical intent from Cypress code.
- reference/mappings.md — per-target translation tables and worked examples.
Read shared references as needed: open-testing-convert/reference/shared/{locator-mapping,wait-strategies,assertion-mapping,lifecycle-mapping}.md.
Emit the converted test(s) according to the target primer's Emission Checklist. Produce a preamble summarising: source file, config version, target, language choice, any TODOs.

Scope

Cypress 10+ (cypress.config.*, .cy.{js,ts} naming) — primary.
Cypress 9 and earlier (cypress.json, integration/**/*.spec.js) — supported; note migration status in preamble.
Mocha BDD idioms (describe, context, it, before, beforeEach, after, afterEach) — native to Cypress.
Custom commands defined in cypress/support/commands.{js,ts} — inline-flatten during extraction.
cy.intercept(...) network stubs / request assertions.
cy.session(...) for auth-state caching.
Cypress Testing Library (@testing-library/cypress), cypress-real-events, cypress-axe, cypress-file-upload — recognise and map.

Out of scope (delegate to sibling skills)

Cypress component testing (cy.mount) — emit with preamble flag; component scope does not map cleanly to Selenium/Playwright E2E or natural-language targets.
Cucumber-over-Cypress (@badeball/cypress-cucumber-preprocessor, or legacy cypress-cucumber-preprocessor) — use open-testing-convert-cucumber, which invokes this skill for the step-implementation layer.

Quick reference: Cypress verbs and their canonical conversions

Cypress	Intent	Conversion hub
`cy.visit(url)`	navigate	`shared/wait-strategies.md` §Navigation
`cy.get(sel).click()`	click	`shared/locator-mapping.md`
`cy.get(sel).type(x)`	text input	`shared/locator-mapping.md`
`cy.contains('X')`	locate by visible text	`shared/locator-mapping.md`
`cy.findByRole('button', {name:'X'})`	Testing Library locator	`shared/locator-mapping.md`
`.should('be.visible')`	assertion (auto-retries)	`shared/assertion-mapping.md`
`cy.intercept(...).as('x'); cy.wait('@x')`	network synchronisation	`shared/wait-strategies.md` §Cypress
`beforeEach(() => ...)`	lifecycle	`shared/lifecycle-mapping.md`

See reference/mappings.md for the full per-target cookbook.