playwright-e2e

Write, review, and debug Playwright end-to-end tests for Next.js/Supabase applications.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/darraghh1/my-claude-setup --skill playwright-e2e-darraghh1
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: playwright-e2e
Source: https://github.com/darraghh1/my-claude-setup/tree/main/.claude/skills/playwright-e2e
Command: npx skills add https://github.com/darraghh1/my-claude-setup --skill playwright-e2e-darraghh1

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you write, review, and debug end-to-end tests for your application, preventing common issues that lead to flaky and unreliable test suites.

Core Features & Use Cases

  • Write Resilient Tests: Creates tests using best practices to avoid common pitfalls like brittle selectors and race conditions.
  • Debug Failures: Analyzes screenshots, traces, and network activity to pinpoint the root cause of failing tests.
  • Improve Test Reliability: Focuses on patterns that ensure tests are stable and trustworthy in CI/CD environments.
  • Use Case: When you need to add automated end-to-end tests for a new user registration flow, or when existing tests are failing intermittently in your pipeline.

Quick Start

Use the playwright-e2e skill to write an end-to-end test for the user login flow.

Frequently Asked Questions about playwright-e2e

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

FAQPage Schema
How do I write reliable Playwright e2e tests for a Next.js application?

Write reliable Playwright e2e tests by avoiding anti-patterns like `page.waitForTimeout()` and brittle selectors. Using proper awaits and resilient locators prevents race conditions, ensuring your Next.js test suite remains maintainable and trustworthy in CI/CD pipelines.

Why are my Playwright e2e tests failing intermittently in CI?

Intermittent Playwright e2e test failures in CI often stem from race conditions caused by missing awaits or `page.waitForTimeout()`. Reviewing tests to eliminate these anti-patterns and using resilient selectors stabilizes your e2e test suite.

What is the best way to debug a failing Playwright test?

Debug a failing Playwright test by analyzing test artifacts like screenshots and trace files. Reviewing these artifacts alongside network activity helps pinpoint the exact root cause of the e2e test failure.

How do I avoid brittle selectors in Playwright end-to-end testing?

Avoid brittle selectors in Playwright end-to-end testing by following best practices that prioritize resilient locators over fragile DOM paths. This prevents common pitfalls and ensures tests remain stable against minor UI changes.

Can I use this approach to test a Supabase authentication flow?

Yes, you can write and debug end-to-end tests for a Supabase authentication flow. The approach supports Next.js and Supabase applications directly, ensuring user registration and login flows are reliable.