review

To find anti-patterns in your Playwright test suite, scan your test files to detect hardcoded waits, missing assertions, and improper selector usage. The audit identifies 20 specific execution and stylistic issues, generating a quality report with actionable refactoring suggestions.

Playwright tests become flaky due to hardcoded waits and missing web-first assertions. Systematically analyzing test files identifies these anti-patterns and coverage gaps, providing a 1-10 quality score and automated suggestions to refactor inefficient test code.

You can audit an entire Playwright test directory at once. The review skill operates across individual files or whole test suites, requiring access to your project's test directory and configuration files to generate comprehensive quality reports.

The best way to prioritize refactoring unreliable Playwright tests is to use an automated scoring system. The audit assigns a 1-10 quality score to each test file based on detected performance bottlenecks and anti-patterns, helping you target the most critical execution issues first.

Playwright code review requires access to your project's test directory and configuration files. Analyzing these files allows the audit to enforce web-first assertion standards and best practices across your test suite.

A limitation of automating Playwright test audits is that the process focuses strictly on identifying anti-patterns, coverage gaps, and performance bottlenecks within test files. It requires existing test directory access and does not generate new tests.