Which automation framework does this skill support?

This skill is specifically optimized for Playwright, utilizing its native fixture system and browser automation capabilities.

Does this skill handle user authentication?

Yes, it provides custom fixtures like adminPage and userPage to handle authenticated contexts automatically during testing.

What is the ComponentFinder pattern?

ComponentFinder is a standardized method for looking up UI elements using data-testids, ensuring tests are less prone to breaking when CSS or HTML structure changes.

How should I organize my test files with this skill?

Tests should be placed in tests/e2e/specs/ and categorized into folders such as smoke, public, user, or admin to follow the skill's conventions.

Playwright E2E Testing

Name: Playwright E2E Testing
Author: JasonPaff

byJasonPaff

•

Security & Testing

Enforces standardized end-to-end testing workflows using Playwright with custom fixtures and Page Object Models.

About

The Playwright E2E Testing skill provides a comprehensive framework for validating complete user flows through robust browser automation. It streamlines the testing process by enforcing the Page Object Model (POM) pattern and utilizing a unique ComponentFinder for stable element selection via data-testids. With built-in support for multiple authentication contexts—such as admin and user roles—and structured test categorization, this skill ensures that web applications remain reliable while reducing the boilerplate code typically associated with complex automation suites.

Key Features

Pre-configured Playwright fixtures for admin, user, and guest contexts
2 GitHub stars
Categorized test organization (smoke, public, user, admin, onboarding)
Standardized Page Object Model (POM) implementation using BasePage
ComponentFinder utility for resilient data-testid lookups
Automatic integration with shared testing-base conventions

Use Cases

Automating complex multi-user authentication and permission flows
Building scalable, maintainable test suites for large-scale web applications
Standardizing element selection logic to reduce test fragility and maintenance

About

Key Features

Pre-configured Playwright fixtures for admin, user, and guest contexts
2 GitHub stars
Categorized test organization (smoke, public, user, admin, onboarding)
Standardized Page Object Model (POM) implementation using BasePage
ComponentFinder utility for resilient data-testid lookups
Automatic integration with shared testing-base conventions

Use Cases

Automating complex multi-user authentication and permission flows
Building scalable, maintainable test suites for large-scale web applications
Standardizing element selection logic to reduce test fragility and maintenance