e2e-testing

Structure Playwright end-to-end tests with Page Object Model and deterministic waits.

Updated Mar 28, 2026
One-click install
npx skills add https://github.com/akirschke15-cmd/Cato-Registry --skill e2e-testing-akirschke15-cmd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: e2e-testing
Source: https://github.com/akirschke15-cmd/Cato-Registry/tree/main/.claude/skills/e2e-testing
Command: npx skills add https://github.com/akirschke15-cmd/Cato-Registry --skill e2e-testing-akirschke15-cmd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of brittle, slow end-to-end tests that fail intermittently and don’t provide enough evidence to debug real production-like flows.

Core Features & Use Cases

  • Playwright E2E patterns with Page Object Model (POM): Organize tests for maintainability by encapsulating locators and page actions in reusable page objects.
  • Production-grade configuration: Use multi-reporter output, trace on retries, screenshots/video behavior, timeouts, and a built-in web server setup for consistent runs.
  • Flaky test containment and root-cause guidance: Quarantine flaky tests, conditionally skip in CI, and replace time-based waits with response/visibility/load-state synchronization.
  • Artifact management for debugging: Capture screenshots, traces, and videos and provide a structured test report layout for quicker triage.
  • Wallet/Web3 and financial flow testing: Mock wallet providers for deterministic connection tests and safely test critical flows without risking real money in production.

Quick Start

Use the e2e-testing skill to generate a Playwright setup that runs browser projects, applies a POM for stable selectors, and produces HTML/JUnit/JSON reports with screenshots, traces, and video retention on failure.

Frequently Asked Questions about e2e-testing

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I fix flaky Playwright E2E tests in CI pipelines?

Fix flaky Playwright E2E tests by replacing time-based waits with deterministic synchronization, waiting for specific responses, visibility, or load states, and quarantining unstable tests in CI-driven pipelines to isolate failures.

What is the Page Object Model pattern in Playwright E2E testing?

The Page Object Model (POM) structures Playwright tests by encapsulating locators and page actions in reusable page objects, ensuring stable selectors and improving end-to-end test maintainability across large test suites.

How do I configure Playwright to capture screenshots, traces, and video artifacts?

Configure Playwright with multi-reporter output, trace on retries, and specific video retention on failure to capture screenshots, traces, and videos, providing a structured test report layout for quicker triage and debugging.

Can I test Web3 wallet connections and financial flows with Playwright?

Yes, test Web3 wallet connections and financial critical paths by mocking wallet providers for deterministic connection tests, allowing you to safely verify flows without risking real money in production environments.

What is the best way to organize Playwright E2E tests for maintainability?

Organize Playwright E2E tests for maintainability by applying the Page Object Model to encapsulate page actions, configuring production-grade timeouts and retries, and structuring tests by authentication, feature, and API endpoint coverage.

Why do my Playwright E2E tests fail intermittently without obvious errors?

Intermittent Playwright test failures often stem from time-based waits instead of response or visibility synchronization; using deterministic waits for specific responses and load states resolves these timing issues.