How does this skill help with flaky Playwright tests?

It identifies anti-patterns like hardcoded timeouts and replaces them with explicit waits and auto-waiting assertions that ensure elements are ready before interaction.

Does this skill support accessibility testing?

Yes, it provides patterns for using semantic roles and ARIA labels to ensure your web application meets accessibility standards during automated tests.

Why should I use getByRole instead of CSS selectors?

CSS selectors are prone to change during UI refactors. getByRole focuses on the user-facing semantics, making your tests more resilient and meaningful.

Can this skill help with mobile testing?

It includes specific guidance and code snippets for configuring viewports and testing responsive designs across different devices and screen sizes.

Playwright Best Practices

Name: Playwright Best Practices
Author: jovermier

byjovermier

Security & Testing

Enhances Claude Code with expert guidance for writing reliable, maintainable, and accessible Playwright end-to-end tests.

About

This skill empowers Claude to act as a senior QA engineer, providing domain-specific implementation patterns for Playwright E2E testing. It helps developers move away from fragile CSS selectors and hardcoded timeouts toward robust strategies like semantic locators, auto-waiting assertions, and built-in accessibility checks. Whether you are generating new test suites from scratch or refactoring existing flaky tests, this skill ensures your automation is deterministic, responsive, and easy to maintain by following industry-standard testing principles.

Key Features

Responsive design testing configurations for mobile and tablet viewports
Test isolation and cleanup patterns for deterministic execution
Explicit wait strategies to eliminate flakiness and hardcoded delays
Semantic selector strategies using getByRole, getByTestId, and getByLabel
Automated accessibility (a11y) testing and keyboard navigation patterns
0 GitHub stars

Use Cases

Generating new Playwright test suites with built-in accessibility support
Refactoring flaky E2E tests to use stable locators and explicit waits
Auditing existing test code for anti-patterns like hardcoded timeouts

About

Key Features

Responsive design testing configurations for mobile and tablet viewports
Test isolation and cleanup patterns for deterministic execution
Explicit wait strategies to eliminate flakiness and hardcoded delays
Semantic selector strategies using getByRole, getByTestId, and getByLabel
Automated accessibility (a11y) testing and keyboard navigation patterns
0 GitHub stars

Use Cases

Generating new Playwright test suites with built-in accessibility support
Refactoring flaky E2E tests to use stable locators and explicit waits
Auditing existing test code for anti-patterns like hardcoded timeouts