e2e

Automate end-to-end testing workflows for Playwright, Cypress, or Selenium projects.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/isaenter/UES-PRO --skill e2e-isaenter
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: e2e
Source: https://github.com/isaenter/UES-PRO/tree/main/frontend-vben/.claude/skills/e2e
Command: npx skills add https://github.com/isaenter/UES-PRO --skill e2e-isaenter

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

End-to-end testing is essential for validating complex user workflows across frameworks like Playwright, Cypress, or Selenium. This Skill provides a structured approach when Path C+ or explicit user requests require automated validation of workflows, ensuring regression coverage and consistent quality.

Core Features & Use Cases

  • Test case authoring based on design.md acceptance criteria
  • Execution with project-specific commands and automatic result logging to quality.md
  • Manual validation checklist when no E2E framework is present, covering key user flows

Quick Start

Configure an E2E test suite, implement cases for core user flows, and run the test suite to verify they pass.

Frequently Asked Questions about e2e

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

FAQPage Schema
How do I automate end-to-end testing workflows for web applications?

Automate end-to-end testing workflows by generating test cases from design.md acceptance criteria, executing them with project-specific commands, and logging results to quality.md for regression coverage.

Does this E2E testing approach work with Playwright, Cypress, and Selenium?

Yes, end-to-end testing supports Playwright, Cypress, and Selenium, validating user journeys across web applications when explicit QA requirements or Path C+ conditions exist.

How do I generate E2E test cases from acceptance criteria?

Generate E2E test cases by supplying a design.md file containing acceptance criteria, which the workflow uses to author and implement cases for core user flows automatically.

What happens if my project does not have an E2E framework configured?

Without an E2E framework, the workflow provides a manual validation checklist covering key user flows to ensure consistent quality and user journey verification.

How are test execution results recorded during end-to-end testing?

Test execution results are recorded by logging outcomes directly to quality.md, using project-specific run commands to execute the suite and verify that core user flows pass.

When should I use automated E2E testing instead of manual validation?

Use automated E2E testing when Path C+ or explicit QA requirements demand regression coverage for complex user workflows, ensuring consistent quality across web applications.