Moving your automated tests from Cypress or Selenium to Playwright can save time and make your test suite stronger. This guide walks you through each step, from finding your current test files to converting them one by one. You will learn how to replace old commands with Playwright equivalents and upgrade your selectors for better results.
The process works for both small and large test suites. You can convert a single file or run a batch conversion for bigger projects. The tool also helps you clean up old dependencies and update your CI workflow after the move.
By following this plan, you keep your tests reliable and easy to maintain. The migration is done file by file so you can check each one before moving on. This reduces errors and makes the switch smooth for your whole team.
Global
mkdir -p ~/.claude/skills/migrateProject
mkdir -p .claude/skills/migrateSource Repository
Grill Memattpocock/skills
Stress-test your plan with relentless questions until we both understand
Tddmattpocock/skills
Write one test at a time then code to make it pass
Test Driven Developmentobra/superpowers
Write a failing test first then code just enough to pass
Qamattpocock/skills
Turn bug reports into GitHub issues through natural conversation without technical fuss
Migrate To Shoehornmattpocock/skills
Replace unsafe as assertions with type-safe partial test data easily
Webapp Testinganthropics/skills
Test your local web apps quickly with Playwright automation and screenshots
Playwright Best Practicescurrents-dev/playwright-best-practices-skill
Master Playwright testing with best practices for reliable and fast tests
Google Agents Cli Evalgoogle/agents-cli
Run evaluations on your AI agent, find failures, and improve its quality step by step