When should I avoid using an E2E test?

Avoid E2E tests for component-specific behavior, validation logic, or edge cases; these are better handled by unit or component tests which are faster to execute.

Which testing frameworks are compatible with these patterns?

The patterns provided—such as Page Object Model and user-centric selectors—are framework-agnostic and work seamlessly with Playwright, Cypress, and Selenium.

How does this skill improve test stability?

It advocates for condition-based waiting instead of arbitrary timeouts and promotes user-centric selectors that survive UI refactors and CSS changes.

What is the 'Iron Law' of E2E testing in this skill?

The Iron Law dictates that E2E tests should be reserved only for critical user journeys, ideally making up only 10-15% of your total test suite to maintain speed and reliability.

Does this skill help with test data management?

Yes, it includes best practices for using factories and fixtures to ensure test isolation and unique data generation, preventing 'flaky' tests caused by shared state.

Frontend E2E User Journeys

Name: Frontend E2E User Journeys
Author: bacchus-labs

bybacchus-labs

•

Seguridad y Pruebas

Automates critical frontend user workflows using resilient end-to-end testing patterns and the Page Object Model.

Acerca de

This skill provides a comprehensive framework for implementing high-quality end-to-end (E2E) tests within Claude Code. It emphasizes the 'Iron Law' of testing, focusing automation efforts on the most critical 10-15% of user workflows such as authentication, checkout, and multi-step onboarding. By guiding users through the Page Object Model (POM), accessibility-first selectors, and condition-based waiting, it helps teams build test suites that are resilient to UI changes, easy to maintain, and highly effective at catching regressions in business-critical logic.

Características Principales

Comprehensive test data management and isolation techniques
User-centric selector strategies based on accessibility roles
Audit-ready workflow announcements for session transparency
3 GitHub stars
Page Object Model (POM) architecture for encapsulated locators
Condition-based waiting patterns to eliminate test flakiness

Casos de Uso

Verifying complex user onboarding and email verification sequences
Testing third-party OAuth authentication and session persistence
Automating multi-page checkout and payment integration flows

Acerca de

Características Principales

Comprehensive test data management and isolation techniques
User-centric selector strategies based on accessibility roles
Audit-ready workflow announcements for session transparency
3 GitHub stars
Page Object Model (POM) architecture for encapsulated locators
Condition-based waiting patterns to eliminate test flakiness

Casos de Uso

Verifying complex user onboarding and email verification sequences
Testing third-party OAuth authentication and session persistence
Automating multi-page checkout and payment integration flows