borghei/Claude-Skills / engineering/playwright-pro
playwright-pro
VerifiedEnd-to-end testing with Playwright: test generation, page objects, locator strategy, flaky- test diagnosis, visual regression, and CI integration. Use when writing E2E tests, fixing flaky tests, or migrating from Cypress/Selenium.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 10.6 KB |
| assets/flawed_tests/profile.spec.ts | script | 468 B |
| assets/reports/run1.json | config | 1.2 KB |
| assets/reports/run2.json | config | 1.3 KB |
| assets/reports/run3.json | config | 1.4 KB |
| assets/sample_flows.json | config | 800 B |
| assets/sample_login.html | other | 489 B |
| assets/tests/login.spec.ts | script | 906 B |
| references/core-rules-and-patterns.md | markdown | 7.2 KB |
| references/diagnosis-migration-and-ci.md | markdown | 8.7 KB |
| references/playwright-patterns.md | markdown | 4.5 KB |
| scripts/coverage_mapper.py | script | 11.0 KB |
| scripts/flaky_detector.py | script | 10.6 KB |
| scripts/page_object_generator.pyexecutable | script | 14.8 KB |
| scripts/test_analyzer.pyexecutable | script | 12.3 KB |
| scripts/test_generator.py | script | 11.1 KB |
| scripts/test_report_parser.pyexecutable | script | 14.8 KB |
| skills/browserstack.md | markdown | 2.4 KB |
| skills/coverage.md | markdown | 1.9 KB |
| skills/fix.md | markdown | 2.6 KB |
| skills/generate.md | markdown | 2.4 KB |
| skills/init.md | markdown | 2.1 KB |
| skills/migrate.md | markdown | 2.5 KB |
| skills/report.md | markdown | 2.0 KB |
| skills/review.md | markdown | 2.2 KB |
| skills/testrail.md | markdown | 2.5 KB |
skills/migrate.md
View on GitHub# Sub-Skill: Migration from Cypress/Selenium
**Parent:** playwright-pro
**Trigger:** "migrate from Cypress", "convert Selenium tests", "switch to Playwright"
## Purpose
Migrate an existing Cypress or Selenium test suite to Playwright. Handles API translation, pattern modernization, and validation of migrated tests.
## Workflow
### Step 1: Audit Existing Suite
Inventory the current test suite:
- Count of test files and test cases
- Frameworks used (Cypress, Selenium WebDriver, Protractor, TestCafe)
- Custom commands and plugins in use
- CI integration points
- Test data management approach
### Step 2: Translate API Calls
Apply the translation table from the parent SKILL.md. Key mappings:
**Cypress to Playwright:**
- `cy.visit()` -> `page.goto()`
- `cy.get()` -> `page.locator()` (then upgrade to `getByRole`)
- `cy.contains()` -> `page.getByText()`
- `cy.intercept()` -> `page.route()`
- `cy.should('be.visible')` -> `expect(locator).toBeVisible()`
- Custom commands -> Page Object methods or fixtures
**Selenium to Playwright:**
- `driver.findElement(By.css())` -> `page.locator()`
- `driver.findElement(By.xpath())` -> `page.getByRole()` (eliminate XPath)
- `WebDriverWait` -> web-first assertions (auto-retry)
- `driver.get()` -> `page.goto()`
### Step 3: Modernize Patterns
During migration, upgrade patterns:
1. Replace CSS/XPath selectors with semantic locators
2. Replace explicit waits with web-first assertions
3. Extract Page Objects from inline locators
4. Replace custom retry logic with Playwright's built-in retries
5. Convert fixture files to proper test data management
### Step 4: Validate Migration
For each migrated test:
1. Run and confirm it passes
2. Compare behavior with the original test
3. Check that no `waitForTimeout` was introduced
4. Verify locator strategy follows priority order
### Step 5: Remove Old Framework
After all tests are migrated and passing:
1. Remove old framework dependencies
2. Update CI configuration
3. Remove old config files (cypress.config.js, etc.)
4. Update documentation and contributing guides
## Inputs
| Input | Required | Description |
|-------|----------|-------------|
| Source framework | Yes | Cypress, Selenium, Protractor, or TestCafe |
| Test directory | Yes | Path to existing test files |
| Priority | No | Migrate all at once or incrementally |
## Outputs
- Migrated Playwright test files
- New Page Object classes
- Updated playwright.config.ts
- Migration report (tests migrated, patterns upgraded, issues found)
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the work | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation code | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |