migrate
alirezarezvani/claude-skills
Migrate Cypress or Selenium test suites to Playwright with file-by-file conversion.
What is migrate?
Automates conversion of Cypress or Selenium test files to Playwright syntax and best practices. Detects your source framework, assesses migration scope, and converts tests sequentially or in batches depending on project size.
- Detects Cypress or Selenium test frameworks automatically
- Counts test files and categorizes migration effort (small/medium/large)
- Converts test syntax: cy.visit() → page.goto(), cy.get() → page.locator(), etc.
- Upgrades selectors to Playwright best practices (role-based, test IDs)
- Converts custom commands and page objects to Playwright fixtures
- Runs converted tests to verify compilation and catch errors
How to install migrate
npx skills add https://github.com/alirezarezvani/claude-skills --skill migrate- Node.js and npm installed
- Existing Cypress or Selenium test suite
- Playwright not yet configured (skill will initialize if needed)
How to use migrate
- 1.Run the skill with optional argument: 'from cypress', 'from selenium', a file path, or leave empty for auto-detection
- 2.Review the migration assessment showing total files, custom commands, and estimated effort
- 3.Allow the skill to set up Playwright if not already present
- 4.Convert files sequentially (small projects) or in batches (medium/large projects)
- 5.Review converted test output and fix any compilation or runtime errors
- 6.Remove old framework dependencies and config files when prompted
- 7.Verify CI workflows are updated to use Playwright
Use cases
- Migrate a Cypress test suite to Playwright for better performance and cross-browser support
- Convert Selenium WebDriver tests to Playwright's modern API
- Upgrade selector strategies from CSS/XPath to role-based locators during migration
- Batch-convert large test suites (30+ files) using parallel processing
- Preserve custom commands and page objects while updating underlying framework
- QA engineers managing test framework upgrades
- Development teams moving from Cypress to Playwright
- Teams using Selenium seeking a more maintainable testing solution
- Projects with large test suites requiring systematic migration
migrate FAQ
Custom commands are converted to Playwright fixtures using test.extend(), preserving their functionality while adapting to Playwright's API.
Yes, the skill detects .py test files with selenium imports and converts them to Playwright syntax.
Cypress fixtures are converted to JSON imports or test data files; Selenium test data is preserved and integrated into the new Playwright structure.
Projects with 31+ files use parallel batch conversion via /batch subagent; medium projects (11-30) are batched in groups of 5.
Yes, the skill updates CI workflows to use Playwright commands and removes old framework references after conversion.
Full instructions (SKILL.md)
Source of truth, from alirezarezvani/claude-skills.
name: "migrate" description: >- Migrate from Cypress or Selenium to Playwright. Use when user mentions "cypress", "selenium", "migrate tests", "convert tests", "switch to playwright", "move from cypress", or "replace selenium".
Migrate to Playwright
Interactive migration from Cypress or Selenium to Playwright with file-by-file conversion.
Input
$ARGUMENTS can be:
"from cypress"— migrate Cypress test suite"from selenium"— migrate Selenium/WebDriver tests- A file path: convert a specific test file
- Empty: auto-detect source framework
Steps
1. Detect Source Framework
Use Explore subagent to scan:
cypress/directory orcypress.config.ts→ Cypressselenium,webdriverinpackage.jsondeps → Selenium.pytest files withseleniumimports → Selenium (Python)
2. Assess Migration Scope
Count files and categorize:
Migration Assessment:
- Total test files: X
- Cypress custom commands: Y
- Cypress fixtures: Z
- Estimated effort: [small|medium|large]
| Size | Files | Approach |
|---|---|---|
| Small (1-10) | Convert sequentially | Direct conversion |
| Medium (11-30) | Batch in groups of 5 | Use sub-agents |
| Large (31+) | Use /batch | Parallel conversion with /batch |
3. Set Up Playwright (If Not Present)
Run /pw:pw-init first if Playwright isn't configured.
4. Convert Files
For each file, apply the appropriate mapping:
Cypress → Playwright
Load cypress-mapping.md for complete reference.
Key translations:
cy.visit(url) → page.goto(url)
cy.get(selector) → page.locator(selector) or page.getByRole(...)
cy.contains(text) → page.getByText(text)
cy.find(selector) → locator.locator(selector)
cy.click() → locator.click()
cy.type(text) → locator.fill(text)
cy.should('be.visible') → expect(locator).toBeVisible()
cy.should('have.text') → expect(locator).toHaveText(text)
cy.intercept() → page.route()
cy.wait('@alias') → page.waitForResponse()
cy.fixture() → JSON import or test data file
Cypress custom commands → Playwright fixtures or helper functions
Cypress plugins → Playwright config or fixtures
before/beforeEach → test.beforeAll() / test.beforeEach()
Selenium → Playwright
Load selenium-mapping.md for complete reference.
Key translations:
driver.get(url) → page.goto(url)
driver.findElement(By.id('x')) → page.locator('#x') or page.getByTestId('x')
driver.findElement(By.css('.x')) → page.locator('.x') or page.getByRole(...)
element.click() → locator.click()
element.sendKeys(text) → locator.fill(text)
element.getText() → locator.textContent()
WebDriverWait + ExpectedConditions → expect(locator).toBeVisible()
driver.switchTo().frame() → page.frameLocator()
Actions → locator.hover(), locator.dragTo()
5. Upgrade Locators
During conversion, upgrade selectors to Playwright best practices:
#id→getByTestId()orgetByRole().class→getByRole()orgetByText()[data-testid]→getByTestId()- XPath → role-based locators
6. Convert Custom Commands / Utilities
- Cypress custom commands → Playwright custom fixtures via
test.extend() - Selenium page objects → Playwright page objects (keep structure, update API)
- Shared helpers → TypeScript utility functions
7. Verify Each Converted File
After converting each file:
npx playwright test <converted-file> --reporter=list
Fix any compilation or runtime errors before moving to the next file.
8. Clean Up
After all files are converted:
- Remove Cypress/Selenium dependencies from
package.json - Remove old config files (
cypress.config.ts, etc.) - Update CI workflow to use Playwright
- Update README with new test commands
Ask user before deleting anything.
Output
- Conversion summary: files converted, total tests migrated
- Any tests that couldn't be auto-converted (manual intervention needed)
- Updated CI config
- Before/after comparison of test run results
Related skills
More from alirezarezvani/claude-skills and the wider catalog.

ms365-tenant-manager
Microsoft 365 tenant administration for Global Administrators. Automate M365 tenant setup, Office 365 admin tasks, Azure AD user management, Exchange Online configuration, Teams administration, and security policies. Generate PowerShell scripts for bulk operations, Conditional Access policies, license management, and compliance reporting. Use for M365 tenant manager, Office 365 admin, Azure AD users, Global Administrator, tenant configuration, or Microsoft 365 automation.

pm-skills
Orchestrate project delivery across 8 PM sub-skills—sprint analytics, portfolio health, Jira, Confluence, admin, templates, meetings, and team comms.

postmortem
Blameless 5-Whys analysis to extract learning from failures and build a change register.

product-manager-toolkit
Comprehensive toolkit for product managers including RICE prioritization, customer interview analysis, PRD templates, discovery frameworks, and go-to-market strategies. Use when prioritizing features, synthesizing user research, writing requirement documentation, or developing product strategy.

product-skills
Orchestrator for 16 product sub-skills: route inquiries to RICE, OKRs, UX research, discovery, analytics, experiments, and more.

product-strategist
Strategic product leadership toolkit for Head of Product covering OKR cascade generation, quarterly planning, competitive landscape analysis, product vision documents, and team scaling proposals. Use when creating quarterly OKR documents, defining product goals or KPIs, building product roadmaps, running competitive analysis, drafting team structure or hiring plans, aligning product strategy across engineering and design, or generating cascaded goal hierarchies from company to team level.