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/fix.md
View on GitHub# Sub-Skill: Fix Failing Tests
**Parent:** playwright-pro
**Trigger:** "fix flaky test", "Playwright test failing", "debug e2e failure"
## Purpose
Diagnose and fix failing or flaky Playwright tests. Uses trace analysis, error pattern matching, and the 10 golden rules to identify root causes and apply fixes.
## Workflow
### Step 1: Reproduce and Classify
Run the failing test with full diagnostics:
```bash
npx playwright test <test-file> --trace on --retries 3 --reporter=list
```
Classify the failure:
- **Deterministic failure:** Fails every time (likely a real bug or broken locator)
- **Flaky failure:** Passes sometimes (timing, state isolation, or environment issue)
- **Environment failure:** Only fails in CI (font rendering, network, resource constraints)
### Step 2: Analyze Trace
Open the trace viewer to inspect the failure point:
```bash
npx playwright show-trace test-results/<test>/trace.zip
```
Check for:
- Element not found at the moment of interaction
- Network request timing vs assertion timing
- Console errors or uncaught exceptions
- Screenshot showing unexpected UI state
### Step 3: Match Error Pattern
| Error Pattern | Root Cause | Fix |
|---------------|-----------|-----|
| `waiting for locator` timeout | Element not rendered or selector wrong | Add `await expect(locator).toBeVisible()` before interaction |
| `strict mode violation` | Multiple elements match locator | Make locator more specific with `.first()`, `.nth()`, or tighter role/name |
| `Target closed` | Page navigated during action | Add `waitForURL()` or `waitForLoadState()` before assertion |
| `net::ERR_CONNECTION_REFUSED` | Dev server not running | Check `webServer` config in `playwright.config.ts` |
| `toHaveScreenshot` mismatch | Visual diff from baseline | Update snapshot or fix the CSS regression |
### Step 4: Apply Fix
Apply the appropriate fix from the pattern table. After fixing:
1. Run the test 5 times locally to confirm stability
2. Run with `--retries 0` to ensure it passes without retries
3. If the fix involved adding a wait, verify it uses web-first assertions (not `waitForTimeout`)
### Step 5: Prevent Recurrence
- Add the failure pattern to team knowledge base
- If the root cause is a common anti-pattern, flag it for the test analyzer
## Inputs
| Input | Required | Description |
|-------|----------|-------------|
| Test file or name | Yes | The failing test to diagnose |
| Error message | No | The error output (speeds up diagnosis) |
| CI vs local | No | Where the failure occurs |
## Outputs
- Root cause diagnosis with evidence
- Applied fix with explanation
- Stability verification (5x pass confirmation)
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 |