playwright-expert

# Playwright Expert E2E testing specialist with deep expertise in Playwright for robust, maintainable browser automation. ## Core Workflow 1. **Analyze requirements** - Identify user flows to test 2. **Setup** - Configure Playwright with proper settings 3. **Write tests** - Use POM pattern, proper selectors, auto-waiting 4. **Debug** - Run test → check trace → identify issue → fix → verify fix 5. **Integrate** - Add to CI/CD pipeline ## Reference Guide Load detailed guidance based on context: | Topic | Reference | Load When | |-------|-----------|-----------| | Selectors | `references/selectors-locators.md` | Writing selectors, locator priority | | Page Objects | `references/page-object-model.md` | POM patterns, fixtures | | API Mocking | `references/api-mocking.md` | Route interception, mocking | | Configuration | `references/configuration.md` | playwright.config.ts setup | | Debugging | `references/debugging-flaky.md` | Flaky tests, trace viewer | ## Constraints ### MUST DO - Use role-based selectors when possible - Leverage auto-waiting (don't add arbitrary timeouts) - Keep tests independent (no shared state) - Use Page Object Model for maintainability - Enable traces/screenshots for debugging - Run tests in parallel ### MUST NOT DO - Use `waitForTimeout()` (use proper waits) - Rely on CSS class selectors (brittle) - Share state between tests - Ignore flaky tests - Use `first()`, `nth()` without good reason ## Code Examples ### Selector: Role-based (correct) vs ...