e2e-testing

Execute Playwright web app tests and generate HTML reports with CI/CD compatibility.

1|Updated Mar 18, 2026
One-click install
npx skills add https://github.com/xxih/ai-harness-zh --skill e2e-testing-xxih
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: e2e-testing
Source: https://github.com/xxih/ai-harness-zh/tree/main/references/translations/everything-claude-code/docs/zh-CN/skills/e2e-testing
Command: npx skills add https://github.com/xxih/ai-harness-zh --skill e2e-testing-xxih

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It eliminates the manual effort of setting up, executing, and maintaining reliable end‑to‑end test suites for web applications, especially handling flaky tests and comprehensive reporting.

Core Features & Use Cases

  • Full Playwright configuration with parallel execution, multi‑browser projects, and CI/CD integration.
  • Page Object Model support for scalable test code organization.
  • Flaky test handling with conditional skips, fixes, and repeat strategies.
  • Artifact management including screenshots, traces, videos, and HTML reports.
  • Use Cases: CI pipelines for web products, cross‑browser regression testing, and stability analysis of critical user flows.

Quick Start

Run the e2e-testing skill on your project to execute all Playwright tests and generate an HTML report.

Frequently Asked Questions about e2e-testing

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

FAQPage Schema
How do I run Playwright E2E tests in a CI/CD pipeline?

Run Playwright E2E tests in a CI/CD pipeline by executing the test suite to generate HTML reports, capture screenshots, and record traces across multiple browsers. This skill configures parallel execution and artifact management for seamless integration.

What is the best way to handle flaky tests in Playwright?

Handling flaky tests in Playwright involves using conditional skips, automated fixes, and repeat strategies. This skill manages flaky test handling to ensure the stability of critical user flows during web application regression testing.

Do I need a Node.js environment to run end-to-end web testing with Playwright?

Yes, you need a Node.js environment with Playwright installed and access to the application's base URL to run end-to-end web testing. This setup allows the skill to execute comprehensive cross-browser test suites.

Can I use a Page Object Model for organizing Playwright test code?

Yes, you can use a Page Object Model for organizing Playwright test code. This skill supports the Page Object Model pattern to provide scalable test code organization for your web application test suites.

How does artifact management work for Playwright cross-browser regression testing?

Artifact management for Playwright cross-browser regression testing works by automatically capturing screenshots, traces, and videos. The skill generates CI/CD compatible HTML reports to help analyze test failures and user flow stability.

Why does my Playwright test suite need parallel execution and multi-browser projects?

Your Playwright test suite needs parallel execution and multi-browser projects to efficiently validate web applications across different environments. This skill provides full Playwright configuration to reduce execution time and ensure cross-browser compatibility.