migrate

Convert Cypress or Selenium test files to Playwright syntax.

Updated Mar 12, 2026
One-click install
npx skills add https://github.com/Fantasia1999/claude-skills-zh --skill migrate-fantasia1999
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: migrate
Source: https://github.com/Fantasia1999/claude-skills-zh/tree/main/translations/engineering-team/playwright-pro/skills/migrate
Command: npx skills add https://github.com/Fantasia1999/claude-skills-zh --skill migrate-fantasia1999

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and scripts (resource) components.

What problem does it solve?

This Skill automates the complex and time-consuming process of migrating existing test suites from Cypress or Selenium to Playwright, ensuring a smoother transition and leveraging Playwright's advanced features.

Core Features & Use Cases

  • Automated Test Conversion: Converts Cypress or Selenium test files to Playwright syntax.
  • Framework Detection: Automatically identifies the source framework (Cypress or Selenium).
  • Step-by-Step Guidance: Provides clear steps for migration, including dependency management and locator upgrades.
  • Use Case: A team is looking to switch from Cypress to Playwright to improve test performance and cross-browser compatibility. This Skill can guide them through converting their existing Cypress test suite, file by file or in batches, minimizing manual effort and potential errors.

Quick Start

Use the migrate skill to convert tests from Cypress to Playwright.

Frequently Asked Questions about migrate

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

FAQPage Schema
How do I migrate e2e testing suites from Cypress to Playwright?

To migrate e2e testing suites from Cypress to Playwright, this Skill detects the source framework, installs Playwright, and converts test files using provided syntax mappings. It guides you through upgrading locators and verifying the converted tests to ensure a smooth transition.

Can I convert Selenium tests to Playwright in batches?

Yes, you can convert Selenium tests to Playwright in batches. The Skill supports both individual file conversion and batch processing for large test suites, allowing you to automate the migration of multiple test files simultaneously while minimizing manual effort.

What is the process for upgrading locators during test migration to Playwright?

Upgrading locators during test migration to Playwright is a guided step within the conversion process. The Skill automatically maps existing Cypress or Selenium selectors to Playwright's locator strategies, ensuring elements are correctly identified after the test files are converted.

Does the migration Skill automatically detect whether my tests are in Cypress or Selenium?

Yes, the migration Skill automatically detects whether your source framework is Cypress or Selenium. By identifying the existing test framework, it applies the correct syntax mappings and conversion rules to accurately translate your test files into Playwright.

What are the steps to convert a test file from Selenium to Playwright syntax?

Converting a Selenium test file to Playwright syntax involves detecting the source framework, assessing scope, installing Playwright, and applying syntax mappings. The Skill then upgrades locators and verifies the converted tests to complete the file migration process.

Why should I switch from Cypress to Playwright for my automation tests?

Switching from Cypress to Playwright for automation tests improves test performance and cross-browser compatibility. This Skill facilitates the transition by automating the conversion of your existing test suite, reducing manual effort and potential errors during the migration.