Engineering TestingPlaywrightMigration

Playwright Pro — Migrate

Migrate tests from Cypress or Selenium to Playwright.

$skillfish add ~skills/playwright-pro-migrate

Real Examples Get Started Models & Context

Real Conversations

See how the Playwright Pro — Migrate skill responds to actual requests. These are representative examples of what your AI agent will produce.

You

We have 40 Cypress spec files, about 180 tests total. Mix of login, dashboard, and CRUD flows. Cypress is getting slow and we want cross-browser coverage. How long will migration take and what's the plan?

Agent

Scoping the migration first. This skill includes executable scripts — I'll need your permission before running them.

Migration Assessment (scanned cypress/ directory):

Total spec files:       40
Total tests:            183
Custom commands:        12  (cypress/support/commands.js)
Fixtures:               8   (JSON files)
Plugins:                2   (cypress-axe, cypress-file-upload)
Estimated effort:       Medium-Large (2–3 sessions)

Migration plan:

Run /pw:init to configure Playwright
Convert files in batches of 8 using parallel sub-agents
Custom commands → Playwright test.extend() fixtures
cypress-axe → Playwright built-in accessibility snapshots
cypress-file-upload → native page.setInputFiles()

Sample conversion:

// BEFORE (Cypress)
cy.visit('/login');
cy.get('[data-cy=email]').type('user@test.com');
cy.get('[data-cy=submit]').click();
cy.url().should('include', '/dashboard');

// AFTER (Playwright — locators upgraded)
await page.goto('/login');
await page.getByTestId('email').fill('user@test.com');
await page.getByRole('button', { name: 'Sign in' }).click();
await expect(page).toHaveURL(/dashboard/);

Locators are upgraded to getByTestId and getByRole during conversion — not a literal cy.get swap.

Estimated: 2–3 sessions for full conversion + verification. Start with Batch 1 (auth files)?

You

Convert this Selenium Python test to Playwright TypeScript:

driver.get('https://app.example.com/products')
driver.find_element(By.CSS_SELECTOR, '.product-card:first-child .btn-add').click()
WebDriverWait(driver, 10).until(EC.text_to_be_present_in_element((By.CSS_SELECTOR, '.cart-count'), '1'))
assert driver.find_element(By.CSS_SELECTOR, '.cart-count').text == '1'

Agent

Here's the converted Playwright TypeScript with upgraded locators and web-first assertions:

test('should add first product to cart', async ({ page }) => {
  await page.goto('/products');  // baseURL from config — no hardcoded domain

  // Upgrade: CSS '.btn-add' → role-based (resilient to class changes)
  await page.getByRole('listitem').first()
    .getByRole('button', { name: /add to cart/i }).click();

  // Upgrade: WebDriverWait + EC.text_to_be_present → web-first (auto-retries)
  await expect(page.getByRole('status', { name: 'Cart' })).toHaveText('1');
});

What changed and why:

Selenium	Playwright	Reason
`find_element(By.CSS_SELECTOR, '.btn-add')`	`getByRole('button', { name: /add to cart/i })`	Role-based survives CSS refactors
`WebDriverWait(10).until(EC.text_to_be_present...)`	`expect(locator).toHaveText('1')`	Auto-retries until timeout; no manual wait
`assert element.text == '1'`	Absorbed into `toHaveText`	Unified assertion, not a two-step pattern
`driver.get('https://app.example.com/...')`	`page.goto('/products')`	`baseURL` in config eliminates hardcoding

Result: 4 lines, zero explicit waits, zero hardcoded URLs. Shall I convert the rest of your Python suite?

Get Started

How to install and use this skill in your preferred environment.

Skills are designed for AI coding agents (Claude Code, Cursor, Windsurf) and IDE-based workflows where the agent can read files, run scripts, and act on your codebase. Web-based AI can use the knowledge and frameworks, but won't have tool access.

Models & Context

Which AI models and context windows work best with this skill.

Recommended Models

Best

Claude Opus 4 Claude Sonnet 4 GPT-4.1 Gemini 2.5 Pro Grok 3 Kimi K2

Good

Claude Haiku 4.5 GPT-4.1 mini Gemini 2.5 Flash Grok 3 mini

Larger models produce more detailed, production-ready outputs.

Context Window

This skill's SKILL.md is typically 3–10 KB — fits in any modern context window.

8K Skill only

32K+ Skill + conversation

100K+ Skill + references + codebase

All current frontier models (Claude, GPT, Gemini) support 100K+ context. Use the full window for complex multi-service work.

Pro tips for best results

1

Be specific

Include numbers — users, budget, RPS — so the skill can size the architecture.

2

Share constraints

Compliance needs, team size, and existing stack all improve the output.

3

Iterate

Start with a high-level design, then ask follow-ups for IaC, cost analysis, or security review.

4

Combine skills

Pair with companion skills below for end-to-end coverage.

Ready to try Playwright Pro — Migrate?

Install the skill and start getting expert-level guidance in your workflow — any agent, any IDE.

$skillfish add ~skills/playwright-pro-migrate

← Browse all 169 skills