e2e-testing-specialist

Validate user workflows and UI interactions with Playwright end-to-end tests.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/Whaleylaw/llm-lawyer --skill e2e-testing-specialist
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: e2e-testing-specialist
Source: https://github.com/Whaleylaw/llm-lawyer/tree/main/.claude/skills/e2e-testing-specialist
Command: npx skills add https://github.com/Whaleylaw/llm-lawyer --skill e2e-testing-specialist

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a reproducible, developer-friendly approach to validate complete user journeys and UI behavior in real browsers so teams can catch regressions and surface flaky or environment-specific bugs before release.

Core Features & Use Cases

  • Cross-browser end-to-end testing: Configure and run tests in Chromium, Firefox, and WebKit to verify browser-specific behavior.
  • User workflow validation: Exercises authentication flows, multi-step forms, navigation, file downloads, dialogs, drag-and-drop, and document creation from a real user perspective.
  • Robust test patterns: Includes guidance on page objects, auth state reuse, network interception for API mocking, async wait strategies, retries, traces, and CI integration to reduce flakiness.
  • Use Case: Verify signup → document creation → dashboard listing across browsers and CI with saved auth state and API mocking for deterministic results.

Quick Start

Run a Playwright end-to-end test suite that verifies signup, login, document creation, and dashboard rendering in a headless Chromium browser.

Frequently Asked Questions about e2e-testing-specialist

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

FAQPage Schema
How do I automate end-to-end testing for authentication flows and multi-page navigation?

End-to-end testing for authentication and multi-page navigation uses automated browser tests to exercise user workflows like login and document creation. You configure auth state fixtures or storageState to validate complete user journeys across multiple pages.

What is the best way to run cross-browser tests for web application UI interactions?

Cross-browser testing for UI interactions verifies browser-specific behavior by running automated tests in Chromium, Firefox, and WebKit. It configures Playwright test environments to validate forms, file downloads, and dialogs across different browser engines.

How do I reduce flakiness in Playwright test automation during CI integration?

Reduce flakiness in Playwright test automation during CI integration by applying async wait strategies, network interception for API mocking, and configuring test retries. Traces and test reporting artifacts help diagnose environment-specific bugs and intermittent failures.

Does Playwright work with network interception for mocking API responses in end-to-end tests?

Yes, Playwright supports network interception for mocking API responses in end-to-end tests. This allows you to mock network requests, ensuring deterministic test results for user workflow validation without relying on live backend services.

Can I reuse authentication state across multiple end-to-end test runs?

Yes, you can reuse authentication state across multiple end-to-end test runs using auth state fixtures or storageState. This approach skips repetitive login workflows, speeding up cross-browser test execution for protected user journeys.

When should I not use real-browser end-to-end tests for UI validation?

Avoid real-browser end-to-end tests for UI validation when checking isolated component logic or running high-frequency unit checks, because browser automation introduces overhead. Use them for complete user journeys and cross-browser compatibility where real browser behavior is required.