skills.rest
andyan77
andyan77COMMUNITY
Explore all skills by this author →
GitHub

diyu-e2e-runner

Coordinate Playwright end-to-end tests, isolate flaky tests, and collect artifacts.

Updated Jul 11, 2026
Search Tags:#testing#reports#e2e#artifacts#playwright#ci#flaky-tests
One-click install
npx skills add https://github.com/andyan77/diyu-agent --skill diyu-e2e-runner
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: diyu-e2e-runner
Source: https://github.com/andyan77/diyu-agent/tree/main/.claude/skills/diyu-e2e-runner
Command: npx skills add https://github.com/andyan77/diyu-agent --skill diyu-e2e-runner

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates end-to-end testing workflows for frontend apps using Playwright, including writing and running tests, isolating flaky tests, collecting artifacts (screenshots, videos, traces), and generating comprehensive reports.

Core Features & Use Cases

  • End-to-end test orchestration with Playwright for modern frontend applications.
  • Flaky test isolation and artifact management to ensure reliable CI signals.
  • CI-ready reporting (HTML and JUnit XML) with trace capture for failing tests.
  • Use Case: Quickly validate critical user journeys after changes and surface debugging artifacts for faster fixes.

Quick Start

Run the Playwright-based E2E runner to execute the current test suite and emit a report.

Frequently Asked Questions about diyu-e2e-runner

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

FAQPage Schema
How do I run Playwright E2E tests and collect artifacts like screenshots and traces?▼

You can run Playwright E2E tests by executing the runner to orchestrate your current test suite, automatically capturing screenshots, videos, and traces as artifacts for debugging failures.

What is the best way to handle flaky tests in a Playwright CI pipeline?▼

Handling flaky tests in a Playwright CI pipeline involves isolating inconsistent test results to maintain reliable CI signals and ensure deterministic behavior across test runs.

How do I generate HTML and JUnit XML reports for Playwright end-to-end tests?▼

To generate HTML and JUnit XML reports for Playwright end-to-end tests, the runner outputs CI-ready reporting formats automatically while capturing execution traces specifically for failing tests.

Does the Playwright E2E runner support regression checks for modern frontend apps?▼

Yes, the Playwright E2E runner supports regression checks for modern frontend apps by validating critical user journeys after changes and coordinating test orchestration to ensure reliable coverage.

Why do I need trace capture for failing tests in end-to-end testing automation?▼

Trace capture for failing tests in end-to-end testing automation is needed to provide debugging artifacts that surface execution steps, enabling faster fixes and reducing regression debugging time.

Related Skills

Explore More Software Engineering Skills→
DemolinatorDemolinator
2

Create E2E Tests

Generate Playwright end-to-end tests with page objects and assertions.

Community
Advanced
orekyuuorekyuu

junit-report-collector

Collect JUnit XML test reports and summarize pass, fail, and skip results.

Community
Intermediate
himanshu231204himanshu231204
2

cpp-testing

Write and configure GoogleTest and CTest for C++17/20 projects.

Community
Intermediate
williamzujkowskiwilliamzujkowski
17

e2e-testing

Automate end-to-end web app testing with Playwright or Cypress in CI/CD pipelines.

Community
Intermediate