swe-developing-e2e-test-with-playwright

What problem does it solve?

AI agents authoring Playwright end-to-end tests frequently produce inconsistent, flaky, and non-compliant test suites that deviate from established best practices, leading to high maintenance overhead and unreliable test results that fail to catch regressions.

Core Features & Use Cases

• Standardized Test Structure: Provides clear guidelines for organizing test files, page objects, and fixtures to ensure consistency across test suites.
• Best Practice Enforcement: Outlines accessibility-first selectors, web-first assertions, and common anti-patterns to avoid to reduce test flakiness and improve maintainability.
• Use Case: A software engineering agent writing E2E tests for a polyglot monorepo's frontend applications can use these standards to create reliable, maintainable test suites that align with the repository's governance requirements.

Quick Start

Use the swe-developing-e2e-test-with-playwright skill to write a new Playwright E2E test for the user login flow that follows accessibility-first selector and web-first assertion standards.