playwright-e2e-design-patterns

What problem does it solve?

This Skill solves the pervasive issue of flaky Playwright E2E tests in full-stack Docker applications, where 90% of developers misdiagnose rate-limit failures as backend bugs. It provides battle-tested patterns for caller IP isolation, resilient fixtures, rich-text editor interaction, and pre-existing failure triage that keep test suites deterministic and maintainable.

Core Features & Use Cases

• Caller IP Isolation: Unique per-test IP injection to prevent rate-limit bucket collisions in parallel E2E runs.
• Resilient Seed-Data Fixtures: Graceful fallback chain that survives seed-data evolution across sprints.
• Rich-Text Editor Testing: Correct paste patterns for Tiptap/ProseMirror editors, avoiding silent image drops.
• Pre-existing Failure Triage: 7-step diagnostic playbook with a 4-option triage table that defaults to fixing real backend bugs instead of skipping tests.
• Tracker-Implementation Divergence: Pattern for reconciling tracker plans with actual implementation without breaking spec alignment.

Quick Start

Use the playwright-e2e-design-patterns skill to audit your current E2E suite for rate-limit flakiness by checking whether all login requests inject unique X-Forwarded-For headers, then apply the per-test IP isolation helper to stabilize the suite.