playwright-migration

Convert Cypress or Selenium/WebDriver tests into Playwright test suites.

347|56|Updated Feb 13, 2026
One-click install
npx skills add https://github.com/testdino-hq/playwright-skill --skill playwright-migration-testdino-hq
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: playwright-migration
Source: https://github.com/testdino-hq/playwright-skill/tree/main/migration
Command: npx skills add https://github.com/testdino-hq/playwright-skill --skill playwright-migration-testdino-hq

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Playwright users need a reliable way to convert existing Cypress or Selenium/WebDriver test suites without rewriting everything blindly.

Core Features & Use Cases

  • Command and pattern mapping: translate common Cypress and Selenium idioms into Playwright equivalents, including navigation, locators, waits, assertions, and interactions.
  • Architecture migration paths: adopt Playwright’s async/await flow, lazy locators, and built-in test runner concepts while changing how tests are structured.
  • Incremental adoption strategy: move from framework-specific helpers (custom commands/page objects and WebDriver waits) to Playwright fixtures and assertions with fewer flake-prone waits.

Use Case: you want to migrate a flaky Cypress suite to Playwright while preserving intent by converting selectors, assertions, intercept/wait patterns, and test setup/teardown into Playwright-native patterns.

Quick Start

Ask the playwright-migration skill to generate a Cypress-to-Playwright conversion plan using the command mapping and mindset shifts described for reliability.

Frequently Asked Questions about playwright-migration

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

FAQPage Schema
How do I migrate Cypress tests to Playwright without rewriting everything?

Playwright migration translates Cypress commands, locators, and assertions into Playwright equivalents while shifting to async/await flow and fixture-based structures, preserving test intent without a blind rewrite.

What is the best way to convert Selenium WebDriver waits to Playwright?

Converting Selenium WebDriver waits to Playwright involves replacing explicit waits with built-in auto-waiting and lazy locators, reducing flake-prone waits by leveraging Playwright's native reliability mechanisms.

Can I incrementally adopt Playwright alongside existing Selenium test suites?

Yes, you can incrementally adopt Playwright by mapping framework-specific helpers and custom commands to Playwright fixtures step-by-step, allowing parallel execution during the transition rather than migrating all tests simultaneously.

How do I map Cypress custom commands and page objects to Playwright architecture?

Mapping Cypress custom commands and page objects to Playwright architecture requires converting them into fixture-based structures and adopting Playwright's async/await flow, replacing framework-specific helpers with native test runner concepts.

Does migrating to Playwright eliminate flaky test waits from Cypress suites?

Migrating to Playwright eliminates flaky waits by replacing Cypress intercept/wait patterns with Playwright's built-in auto-waiting and lazy locators, ensuring reliable assertions without manual timing logic.