review-test-code

Review Playwright tests for flakiness by checking locator quality, waiting strategies, and assertion coverage before execution. This process detects timing issues and anti-patterns in e2e suites, outputting blockers and warnings to prevent non-reproducible test runs.

Test traceability in Playwright suites involves mapping test cases to unique TC-IDs for verification. It ensures every test file aligns with reference cases and project conventions, providing clear tracking of what each e2e test validates across the suite.

Check Playwright test code conventions by extracting patterns from the playwright.config file and reference test cases. Compare your test files against these extracted expectations for locator strategies, setup, teardown, and data handling to ensure adherence.

Yes, you can review an entire Playwright e2e test directory by providing the folder path instead of a single test file. The review checks test isolation, locator quality, and traceability across all files, outputting aggregated blockers and recommendations.

The best way to prevent flaky Playwright locators and timing issues is enforcing a rigorous checklist for locator quality and waiting strategies before test execution. This catches unstable selectors and improper waits, providing warnings and recommendations for correction.

Playwright test review reports blockers for test isolation when tests improperly share state or lack proper setup and teardown. The review verifies isolation against project conventions, flagging tests that may cause non-reproducible execution or data contamination.