e2e-testing

Installation
SKILL.md

E2E Testing

Overview

Covers E2E test architecture and patterns using Playwright — how to structure test suites, organize tests, and apply proven patterns for authentication, mocking, visual regression, accessibility auditing, and CI parallelism. Focuses on the WHY and WHEN of test patterns rather than Playwright API specifics.

When to use: Designing test suite architecture, structuring Page Object Models, planning CI sharding strategies, setting up authentication flows, organizing tests with tags and annotations, implementing visual regression workflows, mocking network requests, auditing accessibility.

When NOT to use: Unit testing (use Vitest/Jest), API-only testing (use integration tests), component testing in isolation (use component test runners). For Playwright API details, browser automation, scraping, or troubleshooting Playwright errors, use the playwright skill.

Quick Reference

Pattern API/Tool Key Points
Role-based locators getByRole, getByText, getByLabel Preferred over CSS/XPath selectors
Page Object Model Classes in tests/pages/ Encapsulate all page-specific locators and actions
Authentication storageState + setup projects Authenticate once, reuse across tests
Visual regression expect(page).toHaveScreenshot() Mask dynamic content to prevent flakes
Accessibility audit AxeBuilder from @axe-core/playwright .withTags() + .analyze() on key flows
Related skills
Installs
53
GitHub Stars
11
First Seen
Feb 20, 2026