migrate

Automate Cypress or Selenium test suite migration to Playwright.

Updated Nov 3, 2016
One-click install
npx skills add https://github.com/xleliberty/mydotfiles --skill migrate-xleliberty
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: migrate
Source: https://github.com/xleliberty/mydotfiles/tree/main/.config/.claude/plugins/cache/claude-code-skills/pw/2.1.2/skills/migrate
Command: npx skills add https://github.com/xleliberty/mydotfiles --skill migrate-xleliberty

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the complex and time-consuming process of migrating legacy test suites from Cypress or Selenium to Playwright, ensuring a smooth transition with minimal manual effort.

Core Features & Use Cases

  • Automated Conversion: Maps legacy commands, locators, and assertions to their modern Playwright equivalents.
  • Framework Detection: Automatically identifies the source framework and assesses the migration scope.
  • Best Practice Upgrades: Replaces brittle selectors with robust, role-based locators and implements Playwright-native fixtures.

Quick Start

Use the migrate skill to convert the existing Cypress test suite in this repository 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 Cypress test suites to Playwright?

Migrating Cypress test suites to Playwright is automated by mapping legacy commands and assertions to modern equivalents. The tool analyzes existing test files to refactor test structure and upgrade locators file-by-file, minimizing manual conversion effort.

Can I convert Selenium tests to Playwright without manual refactoring?

Converting Selenium tests to Playwright is automated by detecting the source framework and mapping legacy commands to Playwright-native APIs. It refactors test structure and replaces brittle selectors with robust locators, requiring minimal manual refactoring for a smooth transition.

Does automated test migration upgrade legacy locators to Playwright standards?

Automated test migration upgrades legacy locators to Playwright standards by replacing brittle selectors with robust, role-based locators. It implements Playwright-native fixtures to ensure modern web testing best practices throughout the converted test suite.

What is the best way to handle test structure refactoring when switching to Playwright?

Handling test structure refactoring when switching to Playwright is best done by analyzing existing configuration and files to map legacy commands to Playwright-native APIs. This supports file-by-file conversion for modern web testing standards.

Does the migration tool support file-by-file conversion for large test suites?

The migration tool supports file-by-file conversion for large test suites. It automatically identifies the source framework, assesses the migration scope, and maps legacy commands to their modern Playwright equivalents to ensure a smooth transition.