菜单
Migrate a Cypress test file (.cy.ts) or Gherkin feature file (.feature) to Playwright following Console's architecture. This is the ONLY skill for Cypress-to-Playwright conversion work, you can perform full migration, analysis-only (--analyze), or dry-run (--dry-run) modes.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/openshift/console --skill migrate-cypress命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
正在显示 SKILL.md
Review changes to the OpenShift Console plugin API for compliance with contribution guidelines, styleguide, and proper documentation in changelogs. Provides a detailed report of findings and compliance score.
Audit all Claude Code skills for stale references, broken paths, and deprecated tool names
Generate React Testing Library tests following OCP Console best practices
基于 SOC 职业分类
| name | migrate-cypress |
| description | Migrate a Cypress test file (.cy.ts) or Gherkin feature file (.feature) to Playwright following Console's architecture. This is the ONLY skill for Cypress-to-Playwright conversion work, you can perform full migration, analysis-only (--analyze), or dry-run (--dry-run) modes. |
| when_to_use | TRIGGER on: "migrate", "convert cypress", "port to playwright", file paths ending in .cy.ts or .feature in a migration context, requests to rewrite Gherkin scenarios as Playwright specs, or explicit /migrate-cypress invocations. Also trigger when user mentions converting "old cypress tests", "remaining e2e tests", or moving test suites from Cypress to Playwright. DO NOT trigger for: writing new Playwright tests from scratch (no Cypress source), fixing or debugging existing .spec.ts files (use debug-test instead), running test suites, editing test infrastructure (base-page.ts, fixtures, KubernetesClient), or questions about Playwright API without migration intent. |
| model | opus |
| argument-hint | <path/to/file.cy.ts or .feature> [--analyze] [--dry-run] |
| allowed-tools | Read, Write, Edit, Bash(find *), Bash(grep *), Bash(ls *), Bash(npx tsc *), Bash(npx playwright *), Bash(git diff *), Bash(git status), mcp__plugin_playwright_playwright__browser_navigate, mcp__plugin_playwright_playwright__browser_snapshot, mcp__plugin_playwright_playwright__browser_click, mcp__plugin_playwright_playwright__browser_console_messages, mcp__plugin_playwright_playwright__browser_take_screenshot, mcp__plugin_playwright_playwright__browser_resize, mcp__plugin_playwright_playwright__browser_run_code_unsafe, mcp__plugin_playwright_playwright__browser_evaluate, mcp__plugin_playwright_playwright__browser_close, mcp__plugin_playwright_playwright__browser_type, mcp__plugin_playwright_playwright__browser_wait_for, mcp__plugin_playwright_playwright__browser_network_requests, AskUserQuestion |
Translate Cypress E2E tests into idiomatic Playwright code following Console's layered architecture. Adapted from openshift-ui-tests-template/migrate.md.
frontend/e2e/.env exists. If missing, copy frontend/e2e/.env.example to frontend/e2e/.env and tell the user to fill in their cluster values before continuing..claude/migration-context.md for the complete API translation tables, structural transformation rules, Console selector mappings, and migration checklist. That file is the single source of truth for all translation context./migrate-cypress <cypress-file-or-feature> — full migration (analyze → implement → validate)/migrate-cypress <cypress-file-or-feature> --analyze — analysis only, produce migration plan/migrate-cypress <cypress-file-or-feature> --dry-run — generate code without writing files/migrate-cypress frontend/packages/integration-tests/tests/cluster-settings/upstream-modal.cy.ts
/migrate-cypress upstream-modal --analyze
/migrate-cypress frontend/packages/dev-console/integration-tests/features/addFlow/ --dry-run
Migrated tests go under e2e/tests/<package>/ based on their source package:
| Source package | Playwright project | Output directory |
|---|---|---|
packages/integration-tests/tests/<area>/ | console | e2e/tests/console/<area>/ |
packages/dev-console/integration-tests/ | dev-console | e2e/tests/dev-console/ |
packages/helm-plugin/integration-tests/ | helm | e2e/tests/helm/ |
packages/knative-plugin/integration-tests/ | knative | e2e/tests/knative/ |
packages/operator-lifecycle-manager/integration-tests/ |
olm |
e2e/tests/olm/ |
packages/topology/integration-tests/ | topology | e2e/tests/topology/ |
packages/webterminal-plugin/integration-tests/ | webterminal | e2e/tests/webterminal/ |
packages/console-telemetry-plugin/integration-tests/ | telemetry | e2e/tests/telemetry/ |
Tests requiring developer auth go in a developer/ subdirectory (e.g. e2e/tests/dev-console/developer/).
.feature files, also resolve step definitions (support/step-definitions/), page actions (support/pages/), and page object selectors (support/pageObjects/).it block or Scenario tests in plain languagefind frontend/e2e/pages frontend/e2e/clients -name "*.ts" 2>/dev/nullExpected output: a structured plan listing each test's intent, the Playwright components to use/create, the isolation strategy, and the output file path.
Stop here if --analyze was specified.
data-test attributes and element rolesIf MCP is unavailable or no cluster is reachable, log a warning: "Playwright MCP not available — selectors translated literally. They may be stale. Run /debug-test after deployment to verify." Proceed to Phase 3.
Locator type from @playwright/test and default-import BasePagegetByTestId() for data-test attributes, locator() for other selectorsdata-test-id, data-test-rows, data-test-dropdown-menu, etc.) but no data-test, add data-test to the React component source and use getByTestId() — never use legacy attribute selectors directlygetX(): Locator), keep locator properties private readonlyrobustClick() inside page objects; specs use plain .click()waitFor() before action methods (fill(), click(), check()) — Playwright auto-waits for actionabilitylegacy prefix — name for what they doExample:
// e2e/pages/cluster-settings.ts
import type { Locator } from "@playwright/test";
import BasePage from "./base-page";
export class ClusterSettingsPage extends BasePage {
private readonly detailsTab = this.page.getByTestId("horizontal-link-Details");
private readonly pageHeading = this.page.getByTestId("cluster-settings-page-heading");
async navigateToDetails(): Promise<void> {
await this.goTo("/settings/cluster");
await this.detailsTab.waitFor({ state: "visible" });
}
getPageHeading(): Locator {
return this.pageHeading;
}
}
import { test, expect } from '../../fixtures'test.describe with tags (e.g. { tag: ['@smoke'] })e2e/tests/<package>/, developer tests in e2e/tests/<package>/developer/test()test.step() for logical grouping when a test has 3+ distinct phasesScenario Outline + Examples: use for...of loop@manual / @broken-test: use test.skip(true, 'reason') or test.fixme('reason') with Jira linknpx tsc --noEmit -p e2e/tsconfig.json and cd frontend && yarn eslint <generated-files> — fix any type or lint errorsPrint code without writing if --dry-run was specified.
npx playwright test --project=<package> <output-file> --retries=0. The project name matches the package directory under e2e/tests/ (e.g. --project=helm, --project=console). For developer tests, use --project=<package>-developer. Add --ui only if the user requests interactive debugging. Note: e2e/.env may override WEB_CONSOLE_URL with a remote cluster URL. If running against localhost, ensure the user has updated e2e/.env or override with WEB_CONSOLE_URL=http://localhost:9000.Migration complete: <source-file> → <output-file>
Tests migrated: N
Page objects created: [list]
Page objects reused: [list]
Files written: [list]
Validation: passed
Test mapping:
| Cypress test | Playwright test | Assertions |
|---------------------------------------|---------------------------------------|------------|
| it('does something') | test('does something') | 3 → 3 |
| it('handles edge case') | test('handles edge case') | 2 → 2 |
| ... | ... | ... |
| Total | | 8 → 8 |
<cypress count> → <playwright count>. If a Playwright test has fewer assertions than its Cypress counterpart, flag it with ⚠ and investigate — assertions may have been silently dropped.it blocks into one test() with test.step()cy.wait(ms) with condition-based waits or assertion timeoutswaitFor() — fill(), click(), check(), etc. auto-wait for actionability; only use waitFor() when waiting for state without acting on the elementcy.exec('oc ...') with KubernetesClientk8sClient.deleteNamespace(), deleteCustomResource(), and deleteClusterCustomResource() already swallow 404 errorsdata-test to React source — when the component only has legacy test attributes (data-test-id, data-test-rows, etc.), add data-test alongside and use getByTestId()If MCP tools fail with "tool not found" or "connection refused": skip Phase 2, translate selectors literally, and warn the user. Selectors can be verified later with /debug-test.
If npx tsc --noEmit reports errors in the generated spec or page object: read the errors, fix missing imports or type mismatches, and re-run. Common causes: missing page object import, wrong fixture type, incorrect KubernetesClient method signature.
Compare assertion count with the original Cypress test. If the migrated test has fewer assertions, the agent may have silently dropped failing ones. Restore them using the intent documented in Phase 1.
.claude/migration-context.md for API translation tables