Migrate to Playwright
Skill Verified ActiveMigrate 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 existing test suites from Cypress or Selenium to Playwright, providing a structured and guided conversion process.
Features
- File-by-file test conversion
- Cypress to Playwright mapping
- Selenium to Playwright mapping
- Locator and command upgrade guidance
- Playwright setup assistance
- Verification and cleanup steps
Use Cases
- Use when migrating a project from Cypress to Playwright.
- Use when migrating a project from Selenium to Playwright.
- Use when converting specific test files between frameworks.
- Use when needing detailed guidance on command and assertion translation.
Non-Goals
- Migrating tests to frameworks other than Playwright.
- Automating the entire migration process without user intervention.
- Writing new Playwright tests from scratch.
Workflow
- Detect Source Framework (Cypress, Selenium, or auto-detect)
- Assess Migration Scope (count files, categorize effort)
- Set Up Playwright (if not present)
- Convert Files (using detailed mappings)
- Upgrade Locators
- Convert Custom Commands / Utilities
- Verify Each Converted File
- Clean Up (dependencies, configs, CI)
Prerequisites
- Playwright needs to be installed or set up.
- User confirmation for file deletion.
- Access to the project's test files and configuration.
Practical Utility
- info:Usage examplesWhile the SKILL.md describes the process and includes command examples for verification, it lacks end-to-end examples demonstrating the input, invocation, and output of the migration itself.
Installation
First, add the marketplace
/plugin marketplace add alirezarezvani/claude-skills/plugin install playwright-pro@claude-code-skillsQuality Score
VerifiedTrust Signals
Similar Extensions
Vue Testing Best Practices
100Use for Vue.js testing. Covers Vitest, Vue Test Utils, component testing, mocking, testing patterns, and Playwright for E2E testing.
Develop Web Game
100Use when Codex is building or iterating on a web game (HTML/JS) and needs a reliable development + testing loop: implement small changes, run a Playwright-based test script with short input bursts and intentional pauses, inspect screenshots/text, and review console errors with render_game_to_text.
Playwright Best Practices
100Use when writing Playwright tests, fixing flaky tests, debugging failures, implementing Page Object Model, configuring CI/CD, optimizing performance, mocking APIs, handling authentication or OAuth, testing accessibility (axe-core), file uploads/downloads, date/time mocking, WebSockets, geolocation, permissions, multi-tab/popup flows, mobile/responsive layouts, touch gestures, GraphQL, error handling, offline mode, multi-user collaboration, third-party services (payments, email verification), console error monitoring, global setup/teardown, test annotations (skip, fixme, slow), test tags (@smoke, @fast, @critical, filtering with --grep), project dependencies, security testing (XSS, CSRF, auth), performance budgets (Web Vitals, Lighthouse), iframes, component testing, canvas/WebGL, service workers/PWA, test coverage, i18n/localization, Electron apps, or browser extension testing. Covers E2E, component, API, visual, accessibility, security, Electron, and extension testing.
Agent Migration Plan
98Agent skill for migration-plan - invoke with $agent-migration-plan
E2E Testing Patterns
98Master end-to-end testing with Playwright and Cypress to build reliable test suites that catch bugs, improve confidence, and enable fast deployment. Use when implementing E2E tests, debugging flaky tests, or establishing testing standards.
Playwright Migration Guides
94Step-by-step migration guides for moving to Playwright from Cypress or Selenium/WebDriver — command mappings, architecture changes, and incremental adoption strategies.