e2e

Start the dev server, wait for readiness, and run Playwright tests with a single worker.

Updated Mar 9, 2026
One-click install
npx skills add https://github.com/alasdairnc/casedive --skill e2e-alasdairnc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: e2e
Source: https://github.com/alasdairnc/casedive/tree/main/.claude/skills/e2e
Command: npx skills add https://github.com/alasdairnc/casedive --skill e2e-alasdairnc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Running Playwright end-to-end tests safely by starting the dev server, waiting for readiness, and executing tests with a single worker first to isolate concurrency issues before scaling up.

Core Features & Use Cases

  • Starts the dev API server if not running and waits for the app to be ready.
  • Runs Playwright tests with a single worker to establish a clean baseline before a full parallel run.
  • Provides guidance for diagnosing flaky tests and scaling up when stability is achieved.

Quick Start

Invoke the /e2e command to start the server, wait for readiness, and run the Playwright tests with a single worker.

Frequently Asked Questions about e2e

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

FAQPage Schema
How do I run Playwright E2E tests safely without concurrency issues?

Run Playwright E2E tests safely by starting the dev API server, waiting for readiness, and executing tests with a single worker (--workers=1) to isolate concurrency issues before scaling up parallel runs.

Why are my Playwright end-to-end tests flaky in CI pipelines?

Flaky tests often stem from concurrency issues or servers not being ready. Running Playwright with a single worker first isolates these failures, establishing a stable baseline before scaling up to full parallel execution.

Do I need npm scripts to automate Playwright end-to-end testing?

Yes, automating Playwright E2E testing requires an npm script for starting the API server (dev:api) and a wait-on utility to detect readiness before executing the test suite.

What is the best way to debug E2E failures across local development and CI?

The best way to debug E2E failures is running Playwright tests with a single worker to isolate concurrency issues, validating feature behavior end-to-end consistently across local development and CI pipelines.

When should I scale up Playwright workers after isolating test failures?

You should scale up Playwright workers after achieving stability with a single worker baseline, using the provided guidance for diagnosing flaky tests before moving to full parallel runs.