Agent skill · software engineering · aiskillstore
e2e-testing-patterns
Master end-to-end testing with Playwright and Cypress to build reliable test suites that catch bugs, improve confidence, and enable fast deployment. Use when implementing E2E tests, debugging flaky tests, or establishing testing standards.
Why this skill is useful
Provides specific Playwright and Cypress patterns and configurations that enhance E2E testing capabilities beyond general knowledge.
What it needs
Requires cypress, playwright installed locally. About 6k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
E2E Testing Patterns Build reliable, fast, and maintainable end-to-end test suites that provide confidence to ship code quickly and catch regressions before users do. When to Use This Skill Implementing end-to-end test automation Debugging flaky or unreliable tests Testing critical user workflows Setting up CI/CD test pipelines Testing across multiple browsers Validating accessibility requirements Testing responsive designs Establishing E2E testing standards Core Concepts 1. E2E Testing Fundamentals What to Test with E2E: Critical user journeys (login, checkout, signup) Complex interactions (drag-and-drop, multi-step forms) Cross-browser compatibility Real API integration Authentication flows What NOT to Test with E2E: Unit-level logic (use unit tests) API contracts (use integration tests) Edge cases (too slow) Internal implementation details 2. Test Philosophy The Testing Pyramid: Best Practices: Test user behavior, not implementation Keep tests independent Make tests deterministic Optimize for speed Use data-testid, not CSS selectors Playwright Patterns Setup and Configuration Pattern 1: Page Object Model Pattern 2: Fixtures for Test Data Pattern 3: Waiting Strategies Pattern 4: Network Mocking and Interception Cypress Patterns Setup and Configuration Pattern 1: Custom Commands Pattern 2: Cypress Intercept Advanced Patterns Pattern 1: Visual Regression Testing Pattern 2: Parallel Testing with Sharding Pattern 3: Accessibility Testing Best Practices 1. Use Data Attributes: data-testid or data-cy for stable selectors 2. Avoid Brittle Selectors: Don't rely on CSS classes or DOM structure 3. Test User Behavior: Click, type, see - not implementation details 4. Keep Tests Independent: Each test should run in isolation 5. Clean Up Test Data: Create and destroy test data in each test 6. Use Page Objects: Encapsulate page logic 7. Meaningful Assertions: Check actual user-visible behavior 8. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/e2e-testing-patterns--9d5d66