e2e-expert

Tests web applications end-to-end using Playwright MCP browser automation.

2|Updated Feb 15, 2026
One-click install
npx skills add https://github.com/SkinnnyJay/simpill-utils --skill e2e-expert-skinnnyjay
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: e2e-expert
Source: https://github.com/SkinnnyJay/simpill-utils/tree/main/.claude/skills/e2e-expert
Command: npx skills add https://github.com/SkinnnyJay/simpill-utils --skill e2e-expert-skinnnyjay

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Manual end-to-end testing of web applications is slow and often misses edge cases, race conditions, accessibility issues, and security vulnerabilities that only surface under rigorous probing. ## Core Features & Use Cases - Comprehensive Test Methodology: Eight-phase workflow covering reconnaissance, core functionality, state management, UI/UX, accessibility, performance, error handling, and security testing. - Playwright MCP Automation: Drives real browser sessions with navigation, screenshots, clicks, form fills, and JavaScript evaluation to capture visual and behavioral evidence. - Structured Test Reports: Produces detailed session reports with severity-rated issues, reproduction steps, screenshot indexes, and prioritized recommendations. - Use Case: Ask it to "test login thoroughly" and it will exercise happy paths plus edge cases like SQL injection attempts, rapid double-submits, session timeouts, and keyboard-only navigation, then deliver a full report with screenshots. ## Quick Start Ask the assistant to test the login flow of your running web app thoroughly, including edge cases and accessibility checks.

Frequently Asked Questions about e2e-expert

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

FAQPage Schema
How do I run end-to-end tests on a web app with Playwright?▼

Point the tester at your running application by configuring the base URL from your playwright.config or package.json scripts. It then navigates pages, fills forms, clicks elements, and captures screenshots to verify behavior across happy paths and edge cases.

What edge cases should E2E tests cover for login forms?▼

Cover empty and invalid inputs, SQL injection and XSS attempts, very long strings, unicode characters, rapid repeated submissions, session timeouts, and multi-tab logout. The skill tests all of these plus case sensitivity and whitespace handling in credentials.

Can Playwright MCP test accessibility and keyboard navigation?▼

Yes, it tabs through interactive elements to verify focus order, tests Enter/Space/Escape activation, checks aria-labels and heading hierarchy, and validates WCAG criteria like 4.5:1 color contrast and 44x44px touch targets.

Does E2E testing with this approach require a specific test environment?▼

No fixed environment is assumed. It reads the project's own configuration for base URL, test accounts, and fixtures, so it works against localhost, staging, or production builds depending on your setup.

Why do E2E tests miss race conditions and how are they caught?▼

Race conditions hide in timing-dependent async operations that scripted assertions overlook. The skill deliberately tests rapid actions, submissions during pending requests, offline/online transitions, and state changes mid-operation to surface them.