pw-review

Topics in the source

• Review Playwright Tests
• Input
• Steps
• 1. Gather Context
• 2. Check Each File Against Anti-Patterns
• 3. Score Each File
• 4. Generate Review Report
• 5. For Project-Wide Review

Systematically review Playwright test files for anti-patterns, missed best practices, and coverage gaps. $ARGUMENTS can be: A file path: review that specific test file A directory: review all test files in the directory Empty: review all tests in the project's testDir Read playwright.config.ts for project settings List all .spec.ts / .spec.js files in scope If reviewing a single file, also check related page objects and fixtures Load anti-patterns.md from this skill directory. Check for all 20 anti-patterns. Critical (must fix): 1. waitForTimeout() usage 2. Non-web-first assertions (expect(await ...)) 3. Hardcoded URLs instead of baseURL 4. CSS/XPath selectors when role-based exists 5. Missing await on Playwright calls 6. Shared mutable state between tests 7. Test execution order dependencies Warning (should fix): 8. Tests longer than 50 lines (consider splitting) 9. Magic strings without named constants 10. Missing error/edge case tests 11. page.evaluate() for things locators can do 12. Nested test.describe() more than 2 levels deep 13. Generic test names ("should work", "test 1") Info (consider): 14. No page objects for pages with 5+ locators 15. Inline test data instead of facto

This is an excerpt. Refer to the complete source and its current requirements.