playwright-best-practices

Flaky Playwright tests are diagnosed using the flaky-tests and debugging references, which cover race conditions, state leaks between tests, and improper waits. Replace explicit waits with auto-retrying assertions and run tests with --repeat-each to verify stability.

Use role-based locators like getByRole and getByLabel instead of CSS selectors, rely on auto-waiting assertions, and structure tests with fixtures or Page Object Model. The Skill's core references cover test structure, locators, and assertions in detail.

Yes, Playwright integrates with @axe-core/playwright to run accessibility scans. The accessibility reference covers AxeBuilder setup, WCAG tag filtering, keyboard navigation tests, ARIA validation, and focus management.

The Skill includes a dedicated pom-vs-fixtures reference for this decision. Fixtures suit shared setup and teardown logic, while Page Object Model works better for encapsulating complex page interactions across many tests.

The infrastructure references cover GitHub Actions, GitLab CI, CircleCI, Azure DevOps, Jenkins, and Docker setups. They include sharding for parallel execution, test reporting, artifact collection, and global setup/teardown configuration.

Yes, the Skill includes dedicated references for Electron desktop apps covering IPC and main/renderer processes, and for browser extensions covering popups, background scripts, and content scripts.