e2e-testing

Orchestrate Playwright tests across UI, API, and authentication boundaries.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/sugar-cat7/ai-avatar-interview --skill e2e-testing-sugar-cat7
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: e2e-testing
Source: https://github.com/sugar-cat7/ai-avatar-interview/tree/main/.agent/skills/e2e-testing
Command: npx skills add https://github.com/sugar-cat7/ai-avatar-interview --skill e2e-testing-sugar-cat7

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Playwright-based end-to-end testing provides a reliable way to validate core user flows in a web application, reducing regressions by exercising UI, API calls, and authentication boundaries with minimal mocks for external systems.

Core Features & Use Cases

  • End-to-end tests that simulate real user interactions across UI and API layers.
  • Reuse of authenticated state via storageState to cover login-required scenarios without re-authentication.
  • Clear guidance for organizing test scenarios and isolating them from internal mocks, while keeping external boundaries realistic.

Quick Start

Run a Playwright-based E2E test suite to verify the most critical user journeys in your staging environment.

Frequently Asked Questions about e2e-testing

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

FAQPage Schema
How do I run Playwright E2E tests across UI and API boundaries?

Playwright E2E tests orchestrate real user interactions across UI and API boundaries by executing test scenarios against a staging environment, validating core user flows while keeping external service mocks to a minimum.

How does storageState work for authenticated Playwright test scenarios?

storageState in Playwright captures and reuses authenticated session data, allowing E2E tests to cover login-required user flows without repeatedly performing re-authentication during regression test execution.

When should I use E2E testing instead of mocking external services?

E2E testing with minimal external mocks is ideal for validating core user flows before releases, ensuring regression coverage for critical user journeys while keeping external boundaries realistic rather than fully isolated.

What is the best way to organize Playwright test scenarios for regression coverage?

Organizing Playwright test scenarios involves isolating internal mocks from external boundaries, reusing authenticated state via storageState, and structuring tests to validate core user flows deterministically before releases.

Does Playwright E2E testing work without mocking external API calls?

Yes, Playwright E2E tests enforce minimal external mocks while exercising realistic external boundaries, allowing you to validate UI, API calls, and authentication boundaries with actual service interactions.

Why are my Playwright E2E tests failing across authentication boundaries?

Failures across authentication boundaries often stem from improper storageState maintenance, requiring deterministic routing and valid session reuse to reliably execute login-required regression scenarios.