e2e-test-orchestrator

Automate Playwright/Cypress end-to-end test planning, execution, and reporting.

1|1|Updated Mar 25, 2026
One-click install
npx skills add https://github.com/penghang1223/niannian-workspace --skill e2e-test-orchestrator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: e2e-test-orchestrator
Source: https://github.com/penghang1223/niannian-workspace/tree/main/e2e-test-orchestrator
Command: npx skills add https://github.com/penghang1223/niannian-workspace --skill e2e-test-orchestrator

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

End-to-end test orchestration and execution to coordinate planning, implementation, execution, debugging, and reporting of automated UI tests.

Core Features & Use Cases

  • Source-code-first locator strategies drive stable Playwright/Cypress test scripts.
  • Automated test planning, script generation, execution, and structured reports.
  • Local and CI workflows with deterministic run modes and robust evidence collection.

Quick Start

Run the e2e-test-orchestrator workflow to plan, implement, execute, and report end-to-end tests.

Frequently Asked Questions about e2e-test-orchestrator

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

FAQPage Schema
How do I orchestrate end-to-end test execution for Playwright and Cypress?

Source-code-first locator strategies generate stable Playwright and Cypress test scripts by analyzing the application source code directly. This approach reduces flaky selectors and ensures your end-to-end tests target resilient element references.

Can I run Playwright test orchestration in Docker and CI environments?

E2E test orchestration automates the full testing workflow by coordinating test planning, script generation, execution, debugging, and structured reporting. This ensures reliable automation for Playwright and Cypress pipelines across local and CI environments.

What is the best way to collect evidence during Cypress E2E test execution?

To generate stable Playwright test scripts, this orchestration workflow applies a source-code-first locator strategy. This ensures your automated UI tests use resilient selectors derived directly from the application source code rather than fragile UI attributes.

Do I need Playwright or Cypress installed to use e2e-test-orchestrator?

E2E test orchestration supports automated fault repair by coordinating test execution and capturing robust evidence like screenshots, logs, and traces. This evidence helps diagnose and fix failing automated UI tests during local or CI pipeline runs.

Why does my E2E test orchestration fail to generate stable Playwright scripts?

Test orchestration provides structured reporting by compiling execution results, screenshots, logs, and traces into a unified output. This allows teams to analyze automated UI test outcomes and debug failures efficiently across local and CI environments.