playwright-e2e

Generate and run Playwright E2E tests from discovered UI routes and interactions.

4|2|Updated Mar 16, 2026
One-click install
npx skills add https://github.com/nickhou1983/UI-test-Demo --skill playwright-e2e-nickhou1983
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: playwright-e2e
Source: https://github.com/nickhou1983/UI-test-Demo/tree/main/.github/skills/playwright-e2e
Command: npx skills add https://github.com/nickhou1983/UI-test-Demo --skill playwright-e2e-nickhou1983

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Playwright E2E Testing helps teams quickly generate and run end-to-end tests for frontend apps, ensuring consistent behavior across routes and UI states.

Core Features & Use Cases

  • Generate and run Playwright-based end-to-end tests for web apps using discovered routes and interactions.
  • Validate navigation, form interactions, i18n switching, and multi-step user journeys with deterministic test generation.
  • Align tests with a shared E2E discovery contract to ensure reliable, up-to-date test coverage reflecting the current app state.

Quick Start

Generate and run Playwright tests for all discovered routes and interactions.

Frequently Asked Questions about playwright-e2e

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

FAQPage Schema
How do I automate Playwright E2E tests for frontend applications?

You can automate Playwright E2E tests by generating and executing test scripts that validate navigation, form interactions, and multi-page user journeys based on discovered routes and interactions.

What is a UI discovery payload and do I need it for Playwright E2E testing?

A UI discovery payload provides the discovered routes and interactions required for deterministic test generation. You need this existing payload, alongside runtime DOM exploration when needed, to generate accurate tests.

Can I validate i18n switching and multi-step user journeys with Playwright E2E tests?

Yes, Playwright E2E tests can validate i18n switching, navigation verification, form interactions, and multi-step user journeys by applying a shared discovery contract to ensure reliable test coverage.

How do I ensure my E2E tests reflect the current app state across routes?

Align your tests with a shared E2E discovery contract to ensure reliable and up-to-date test coverage. This guarantees generated tests consistently reflect the current application state and UI interactions.

What's the best way to generate deterministic E2E tests for web apps?

The best way to generate deterministic E2E tests is using a shared discovery contract that maps discovered routes and interactions, ensuring consistent behavior validation across all frontend UI states.

When should I use runtime DOM exploration for frontend E2E testing?

Use runtime DOM exploration when the existing UI discovery payload is insufficient. This approach, driven by ui-test or ui-test-discovery, supplements static data to capture dynamic UI interactions during test generation.