e2e-testing

Plan and execute end-to-end tests with Playwright and MCP server.

Updated Feb 6, 2026
One-click install
npx skills add https://github.com/wtah/spec-master --skill e2e-testing-wtah
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: e2e-testing
Source: https://github.com/wtah/spec-master/tree/main/.claude/skills/e2e-testing
Command: npx skills add https://github.com/wtah/spec-master --skill e2e-testing-wtah

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Solves end-to-end testing planning and execution for full-stack applications.

Core Features & Use Cases

  • Structured Test Planning: Defines roles (E2E Test Planner and E2E Test Developer) and delivers a comprehensive .e2e-tests/test-plan.md.
  • Playwright-Driven Automation: Implements individual test cases against the MCP server to validate frontend-backend integration.
  • Local Development Focus: Default LOCAL_RUN mode bypasses authentication for rapid test development and debugging.

Quick Start

Review product journeys and requirements, generate the test plan at .e2e-tests/test-plan.md, then implement tests with Playwright using the MCP server.

Frequently Asked Questions about e2e-testing

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

FAQPage Schema
How do I plan and execute Playwright E2E tests for a full-stack application?

To plan Playwright E2E tests, map user journeys and requirements into a structured test plan at .e2e-tests/test-plan.md, then implement automated test cases against the MCP server to validate frontend-backend integration.

What is the best way to structure end-to-end testing for local development?

The best way to structure end-to-end testing for local development is to use a default LOCAL_RUN mode, which bypasses authentication to enable rapid test development and debugging of user journeys.

Do I need an MCP server to run Playwright automation tests?

Yes, you need MCP server integration to run these Playwright automation tests, as the test cases are implemented against the MCP server to validate full-stack frontend-backend integration.

How does LOCAL_RUN mode affect Playwright E2E test execution?

LOCAL_RUN mode affects Playwright E2E test execution by bypassing authentication barriers by default, which streamlines the process for rapid test development and debugging in local environments.

What is included in an E2E test plan for full-stack applications?

An E2E test plan for full-stack applications includes defined roles for an E2E Test Planner and Developer, mapped product requirements, user journeys, and container/specs guidance, delivered as a comprehensive markdown file.

Can I use this approach for infrastructure testing with Playwright?

Yes, you can use this Playwright approach for infrastructure testing, as it supports local development or infrastructure testing through MCP server integration and container/specs guidance.