migrate

Migrate Cypress or Selenium test suites to Playwright with file-by-file conversion.

Updated Apr 9, 2026
One-click install
npx skills add https://github.com/Patasse97/claude-skills --skill migrate-patasse97
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: migrate
Source: https://github.com/Patasse97/claude-skills/tree/main/engineering-team/playwright-pro/skills/migrate
Command: npx skills add https://github.com/Patasse97/claude-skills --skill migrate-patasse97

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Migrate Cypress or Selenium test suites to Playwright with file-by-file automated conversion.

Core Features & Use Cases

  • Detect source framework and scope: identify Cypress, Selenium/WebDriver setups.
  • File-by-file conversion: transform tests and configs to Playwright syntax and structure.
  • Verification: validate converted tests and adjust locators for Playwright best practices.

Quick Start

Migrate the Cypress test suite to Playwright by converting files automatically.

Frequently Asked Questions about migrate

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

FAQPage Schema
How do I migrate Cypress tests to Playwright automatically?

You can migrate Cypress tests to Playwright by using file-by-file automated conversion. The process detects your source framework, assesses the migration scope, transforms test files and configs, upgrades selectors, and verifies the converted tests.

Can I convert Selenium test suites to Playwright using this approach?

Yes, you can convert Selenium test suites to Playwright. The conversion process supports JavaScript, TypeScript, and Python test suites, transforming existing Selenium or WebDriver setups into Playwright syntax and structure automatically.

What is the process for converting test configs to Playwright syntax?

Converting test configs to Playwright syntax involves detecting the source framework's configuration files and transforming them file-by-file. This ensures the new Playwright setup aligns with your existing repository structure and related test utilities.

Does the migration process upgrade selectors for Playwright best practices?

Yes, the migration process upgrades selectors to follow Playwright best practices. After converting files and configs, it validates the converted tests and adjusts locators to ensure they work correctly within the Playwright framework.

What programming languages are supported when migrating tests to Playwright?

When migrating tests to Playwright, JavaScript, TypeScript, and Python test suites are supported. The conversion applies to repositories containing Cypress or Selenium tests, config files, and related utilities written in these languages.

Why should I verify converted tests after migrating to Playwright?

Verifying converted tests after migrating to Playwright ensures that the automated file-by-file conversion and selector upgrades function correctly. This validation step confirms that the transformed tests and configs operate as expected in the new framework.