Can I use this to debug existing test failures?

Absolutely. Claude can use these rules to analyze your test code and identify where incorrect locator strategies or network timing issues are causing failures.

What locator strategies does it prioritize?

It prioritizes user-visible attributes like getByRole, getByLabel, and getByText to ensure tests remain resilient even when the underlying HTML structure changes.

How does this skill help reduce flaky tests?

It enforces web-first assertions and discourages hard-coded timeouts, ensuring tests wait naturally for the UI to reach the desired state before proceeding.

Does it support Page Object Models?

Yes, it includes specific rules and organizational patterns for creating maintainable Page Objects that separate page structure from test logic.

Playwright E2E Testing Rules

Name: Playwright E2E Testing Rules
Author: Montinou

byMontinou

Security & Testing

Standardizes Playwright end-to-end test development by enforcing high-performance locators, web-first assertions, and reliable async patterns.

About

This skill provides Claude with a comprehensive set of domain-specific guidelines for writing, reviewing, and debugging Playwright end-to-end tests. It emphasizes 'web-first' assertions and robust locator strategies—such as prioritizing ARIA roles and labels—to eliminate common pitfalls like flaky tests, brittle selectors, and improper wait states. Whether you are scaffolding new test files or refactoring existing suites, this skill ensures your automation code is maintainable, stable, and follows industry-leading Playwright standards for reliable browser automation.

Key Features

Assists in debugging failures by identifying violations of Playwright best practices.
0 GitHub stars
Enforces reliable locator strategies using ARIA roles, labels, and test IDs.
Eliminates anti-patterns like hard-coded timeouts in favor of auto-waiting.
Implements web-first assertions to maximize test stability and reduce flakiness.
Provides structural guidance for Page Object Models and test organization.

Use Cases

Scaffolding new Playwright .spec.ts files with industry-standard syntax.
Refactoring flaky tests to use more resilient locator and wait patterns.
Conducting automated code reviews of test suites to ensure best practices.

About

Key Features

Assists in debugging failures by identifying violations of Playwright best practices.
0 GitHub stars
Enforces reliable locator strategies using ARIA roles, labels, and test IDs.
Eliminates anti-patterns like hard-coded timeouts in favor of auto-waiting.
Implements web-first assertions to maximize test stability and reduce flakiness.
Provides structural guidance for Page Object Models and test organization.

Use Cases

Scaffolding new Playwright .spec.ts files with industry-standard syntax.
Refactoring flaky tests to use more resilient locator and wait patterns.
Conducting automated code reviews of test suites to ensure best practices.