e2e-ui-execute

Orchestrate sequential Playwright UI tests and generate bilingual bug reports.

1|Updated Dec 8, 2025
One-click install
npx skills add https://github.com/specvital/infra --skill e2e-ui-execute
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: e2e-ui-execute
Source: https://github.com/specvital/infra/tree/main/.claude/skills/e2e-ui-execute
Command: npx skills add https://github.com/specvital/infra --skill e2e-ui-execute

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill orchestrates end-to-end UI testing for web applications using Playwright MCP. It guides the tester through prerequisites, sequential test execution, bug reporting, and documentation generation, ensuring tests are performed safely and thoroughly.

Core Features & Use Cases

  • Sequential execution: Runs tests one by one in a defined order to avoid flaky concurrency.
  • Manual verification via Playwright MCP: Facilitates guided manual verification and snapshot capture during each test.
  • Bilingual bug reports: Automatically generates bug reports in Korean and English when issues are found.
  • Documentation generation: Produces per-test summaries and artifacts to track progress and coverage.
  • Environment awareness: Reads project configuration from playwright.config.ts and package.json to discover test dirs and base URLs, and uses those settings for code generation.

Quick Start

Run the UI E2E execution workflow to validate UI behavior across scenarios. Ensure the prerequisites exist: a target document docs/e2e-ui/test-targets.md, a valid Playwright configuration (playwright.config.ts or playwright.config.js), and a package.json with framework dependencies. Start the process with the command to execute tests (e.g., /e2e-ui:execute) and follow the prompts to proceed through tests one at a time.

Frequently Asked Questions about e2e-ui-execute

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

FAQPage Schema
How do I run sequential UI E2E tests to avoid flaky concurrency?

You need a target document `docs/e2e-ui/test-targets.md`, a valid `playwright.config.ts` or `playwright.config.js`, and a `package.json` with framework dependencies. These files provide the test directories and base URLs required to run sequential UI E2E tests.

How does Playwright MCP facilitate manual verification during UI testing?

Playwright MCP facilitates manual verification by guiding testers through snapshot capture and validation during each sequential test. It reads project configuration to discover test directories and uses those settings for code generation and UI behavior validation.

Can I generate bilingual bug reports automatically when E2E tests fail?

Yes, bilingual bug reports are automatically generated in Korean and English when issues are found during sequential UI E2E testing. This ensures comprehensive bug reporting for diverse development teams without manual translation effort.

Does sequential UI testing work with my existing Playwright configuration?

Sequential UI testing works with existing Playwright configurations by reading `playwright.config.ts` and `package.json` to discover test directories and base URLs. It uses those settings for environment awareness and code generation.

What documentation is generated after completing sequential UI E2E test execution?

Sequential UI E2E test execution produces per-test summaries and artifacts to track progress and coverage. This documentation generation helps maintain visibility into test results and validates UI behavior across scenarios.