playwright-best-practices

Playwright E2E test best practices involve using resilient locators, avoiding hardcoded timeouts, and leveraging auto-waiting mechanisms. This Skill maps your current testing activity to curated references that reduce flakiness and improve maintainability across your suite.

Debug a failing Playwright test by utilizing the built-in debugger, Playwright Inspector, and trace viewer. This Skill provides action-oriented guidance and decision trees that map your debugging activity to structured reference patterns for faster troubleshooting.

Yes, this Playwright guidance covers API and accessibility testing patterns alongside E2E and component testing. It provides a broad catalog of topics, mapping your specific testing activity to appropriate best-practice references across all Playwright-supported domains.

The best way to configure Playwright for CI/CD pipelines involves optimizing test execution, parallelization, and shard management. This Skill applies curated infrastructure references to help you speed up CI pipelines and maintain consistent test configurations.

Brittle Playwright locators often stem from relying on CSS or XPath tied to implementation details. This Skill guides you toward robust testing patterns by mapping your selectors to best-practice references that prioritize user-facing attributes and resilient locator strategies.