e2e-testing-automation

Coordinates end-to-end tests via Playwright, Cypress, or Selenium using background sub-agents.

Updated Apr 3, 2026
One-click install
npx skills add https://github.com/Fenghaze/my-skill --skill e2e-testing-automation-fenghaze
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: e2e-testing-automation
Source: https://github.com/Fenghaze/my-skill/tree/main/e2e-testing-automation
Command: npx skills add https://github.com/Fenghaze/my-skill --skill e2e-testing-automation-fenghaze

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

End-to-end testing across the full stack is often time-consuming and error-prone; this Skill provides a structured approach and automation strategy to orchestrate E2E tests across frontend and backend systems, ensuring reliable user journeys.

Core Features & Use Cases

  • Sub-agent driven execution: all E2E tasks run in a background sub-agent to keep the main context clean.
  • Cross-tool support: capable of orchestrating tests with Playwright, Cypress, or Selenium, including reporting.
  • Use cases include regression suites, critical path validation, multi-browser testing, and flaky test mitigation.

Quick Start

Provide your test scope and commands, and I will run all E2E tests in a background sub-agent.

Frequently Asked Questions about e2e-testing-automation

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

FAQPage Schema
How do I automate end-to-end testing for multi-step user journeys?

Automate end-to-end testing by analyzing user journeys and orchestrating test execution via background sub-agents. This approach coordinates cross-browser tests for login and checkout flows, ensuring reliable validation across frontend and backend integrations.

How do I run E2E tests with Playwright or Cypress without cluttering my main context?

Run E2E tests by delegating execution to a background sub-agent, which keeps your main context clean. Provide your test scope and commands, and the sub-agent will orchestrate the tests and return clear reporting.

Can I use this for cross-browser regression checks across frontend and backend integrations?

Yes, you can use this for cross-browser regression checks across frontend and backend integrations. It applies to critical path validation, multi-browser testing, and flaky test mitigation with safe, isolated execution.

What is the best way to orchestrate E2E test automation across different frameworks like Selenium?

The best way to orchestrate E2E test automation is using a sub-agent driven approach that selects appropriate frameworks like Selenium, Cypress, or Playwright. It enforces safe, isolated execution and provides robust test orchestration with clear reporting.

Why do my automated E2E tests fail during critical path validation and how can I mitigate flaky tests?

Automated E2E tests fail during critical path validation due to integration issues, but mitigating flaky tests is achievable through structured sub-agent orchestration. This enforces safe, isolated execution and robust test orchestration to stabilize results.