e2e-testing

Configure Playwright E2E suites with Page Object Model and CI-ready reporting.

1|Updated Mar 6, 2026
One-click install
npx skills add https://github.com/khetansarvesh/ai_skills_repo --skill e2e-testing-khetansarvesh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: e2e-testing
Source: https://github.com/khetansarvesh/ai_skills_repo/tree/main/skills/e2e-testing
Command: npx skills add https://github.com/khetansarvesh/ai_skills_repo --skill e2e-testing-khetansarvesh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of flaky, slow, and hard-to-maintain end-to-end tests by providing practical Playwright patterns that produce reliable results across local and CI environments.

Core Features & Use Cases

  • Playwright E2E test organization: Defines a maintainable tests/ structure (auth, features, API) that scales as your app grows.
  • Page Object Model (POM): Encapsulates selectors and user flows in page objects to reduce duplication and improve readability.
  • Configuration, CI/CD, and reporting: Sets up deterministic runners with retries, parallelism controls, webServer integration, and artifact uploads (HTML reports, screenshots, traces).
  • Flaky test identification and quarantine: Uses repeat runs, retries, fixme/skip strategies, and targeted waiting rules to isolate and resolve instability.
  • Artifacts and diagnostics: Captures screenshots, traces, and videos on failure for quick debugging.
  • Special-case flows: Includes patterns for wallet/Web3 UI mocking and production-safety for critical financial flows.

Quick Start

Generate a complete Playwright E2E suite using the Page Object Model, a CI-ready playwright.config.ts, and a flaky-test strategy with artifacts enabled.

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/CD pipelines?

Fix flaky Playwright E2E tests by applying deterministic waiting strategies using locators and specific network responses, configuring retries, and quarantining unstable tests with fixme/skip to isolate instability in CI/CD pipelines.

What is the best way to structure Playwright tests using the Page Object Model?

Structure Playwright tests using the Page Object Model by organizing files into auth, features, and API directories, encapsulating selectors and user flows within page objects to reduce duplication, and scaling maintainability as your web application grows.

How do I capture screenshots and traces for failed Playwright tests?

Capture screenshots and traces for failed Playwright tests by configuring comprehensive artifact reporting outputs in your Playwright configuration, enabling automatic video and trace retrieval to quickly debug E2E test failures across local and CI environments.

Why does Playwright networkidle waiting cause brittle E2E test suites?

Playwright networkidle waiting causes brittle E2E test suites when applications maintain persistent network connections, requiring a shift to robust waiting strategies based on specific locators or API response assertions to ensure deterministic test execution.

Can I use Playwright for Web3 and financial application E2E testing?

Yes, you can use Playwright for Web3 and financial E2E testing by applying special-case patterns for wallet UI mocking and implementing production-safety rules to secure critical financial flows during end-to-end test execution.

How do I configure parallelism and webServer integration in Playwright config?

Configure parallelism and webServer integration in playwright.config.ts by setting up deterministic runners, defining parallelism controls, and linking the webServer integration to automatically start local development servers during CI/CD test execution.