e2e-testing

Automate Playwright end-to-end tests with Page Object Model patterns and CI artifact capture.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/caovinhphuc/React-OAS-Integration-v4.0 --skill e2e-testing-caovinhphuc
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: e2e-testing
Source: https://github.com/caovinhphuc/React-OAS-Integration-v4.0/tree/main/.claude/skills/e2e-testing
Command: npx skills add https://github.com/caovinhphuc/React-OAS-Integration-v4.0 --skill e2e-testing-caovinhphuc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

End-to-end testing for modern web applications is often flaky, slow, and hard to maintain; this Skill provides Playwright-based patterns and a structured approach to build reliable, scalable end-to-end test suites.

Core Features & Use Cases

  • Page Object Model (POM) implementation to encapsulate UI interactions and promote test reuse.
  • CI/CD-ready configuration with automated test execution, reporting, and artifact capture.
  • Artifact management through automatic screenshots, traces, and videos to accelerate debugging.
  • Flaky-test strategies including quarantine patterns and retry policies to stabilize CI runs.
  • Clear guidance for organizing tests across features, scenarios, and API interactions.

Quick Start

Install dependencies and run the Playwright tests in your CI to validate core end-to-end flows.

Frequently Asked Questions about e2e-testing

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

FAQPage Schema
How do I structure Playwright end-to-end tests using the Page Object Model?▼

Implement the Page Object Model (POM) in Playwright to encapsulate UI interactions and promote test reuse. This structured approach separates page logic from test assertions, creating maintainable and scalable end-to-end test suites for modern web applications.

What is the best way to manage flaky tests in Playwright CI/CD pipelines?▼

Manage flaky Playwright tests by applying quarantine patterns and configuring retry policies. This stabilizes CI runs by isolating inconsistent tests and automatically re-running them, reducing false negatives in your end-to-end test automation workflow.

How do I capture screenshots, traces, and videos as artifacts in Playwright?▼

Capture Playwright artifacts like screenshots, traces, and videos through automated test configuration. This generates debugging outputs during test runs, accelerating issue resolution by providing visual and interactive execution logs for failed scenarios.

Can I run Playwright end-to-end tests across local development and CI/CD environments?▼

Yes, Playwright end-to-end tests are fully configurable for both local development and CI/CD pipelines. This enables consistent automated test execution, reporting, and artifact capture across different environments for stable validation runs.

Does Playwright end-to-end testing support frontend apps with authentication and dynamic content?▼

Yes, Playwright end-to-end testing applies to frontend applications handling authentication, API interactions, and dynamic content. It provides patterns to automate robust workflows and validate complex user scenarios across modern web apps.

Why are my Playwright end-to-end tests slow and hard to maintain?▼

Playwright tests become slow and hard to maintain without structured patterns. Applying Page Object Model organization, configurable test suites, and artifact management builds reliable, scalable end-to-end test suites that resolve these issues.