
Migrate to Playwright
FreeSeamlessly transition tests from Cypress or Selenium to Playwright.
Free · Opens the source repo
What Migrate to Playwright does
Migrate to Playwright is a specialized tool designed for developers looking to transition their test suites from Cypress or Selenium to Playwright. This skill automates the migration process, providing a structured approach to converting existing tests file-by-file. By detecting the source framework and assessing the migration scope, it ensures a smooth transition with minimal manual intervention required.
The migration process begins with an automatic detection of the source framework, whether it be Cypress or Selenium, based on the project structure and configuration files. Once identified, the skill categorizes the number of test files and provides an estimate of the effort required for migration. This allows users to plan their migration strategy effectively, whether they have a small, medium, or large test suite.
As the conversion progresses, the skill applies predefined mappings to translate test commands from Cypress or Selenium into their Playwright equivalents. It also encourages best practices by upgrading locators during conversion, ensuring that the resulting Playwright tests are optimized for performance and maintainability. After each file is converted, users can verify the results through automated testing commands, ensuring that the new tests function correctly before proceeding.
Finally, the skill assists in cleaning up the project by removing old dependencies and configuration files, updating CI workflows, and providing a summary of the migration. This comprehensive approach not only simplifies the migration process but also helps maintain the integrity of the test suite throughout the transition.
When to use it
Use this tool when you need to migrate existing test suites to Playwright for better performance or additional features.
When not to use it
This skill is not suitable for projects that do not use Cypress or Selenium, or for users looking for a one-size-fits-all solution without understanding the specifics of their test frameworks.
What you can build with it
Migrating a Small Test Suite
If you have a test suite with fewer than 10 files, you can use this skill for a straightforward sequential conversion.
Batch Converting Medium Tests
For test suites with 11 to 30 files, utilize the batch processing feature to handle groups of files efficiently.
Transitioning a Large Test Suite
When dealing with over 30 files, the skill allows for parallel conversion, significantly reducing the time required for migration.
How to install Migrate to Playwright
View source1. Install with the skills CLI
npx skills add alirezarezvani/claude-skills/migrate --agent claude-code2. Or install it manually
Download the skill folder and drop it into ~/.claude/skills/ for all projects, or .claude/skills/ to scope it to one repo. Restart Claude Code so it picks up the new skill.
Anthropic's agentic coding CLI, and the reference implementation of Agent Skills. Drop a skill folder into ~/.claude/skills and Claude Code loads it automatically whenever a task matches the skill's description. Claude Code docs
Inside SKILL.md
Written by alirezarezvaniMigrate 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: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
Frequently asked questions about Migrate to Playwright
Similar skills
React Composition Patterns
Streamline your React component architecture with proven patterns.
Pester Should Migration
Easily convert Pester v5 assertions to v6 syntax.
Radix to Base UI Migration
Seamlessly migrate React components from Radix UI to Base UI.
Migrate Next.js to Vinext
Seamlessly transition your Next.js projects to Vinext.
WinUI 3 Migration Guide
Streamline your UWP to WinUI 3 migration process.
Refactor
Enhance code maintainability without altering behavior.
