skills.rest
alasdairnc
alasdairncCOMMUNITY
Explore all skills by this author →
GitHub

e2e-verify

Start the dev API server and run Playwright tests with root-cause failure reports.

Updated Mar 9, 2026
Search Tags:#playwright#ci-cd#e2e-testing#root-cause-analysis#dev-ops#testing-automation
One-click install
npx skills add https://github.com/alasdairnc/casedive --skill e2e-verify-alasdairnc
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: e2e-verify
Source: https://github.com/alasdairnc/casedive/tree/main/.claude/skills/e2e-verify
Command: npx skills add https://github.com/alasdairnc/casedive --skill e2e-verify-alasdairnc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates end-to-end validation by starting the dev API server and running the Playwright test suite, ensuring regressions are caught before deployment.

Core Features & Use Cases

  • Start the API server and verification workflow with a single command.
  • Run the full Playwright test suite and collect failures with structured root-cause analysis.
  • Use during pre-deploy checks or after API/component changes to quickly identify instability and bottlenecks.

Quick Start

Run e2e-verify to start the dev server, run all Playwright tests, and report any failures with root-cause details.

Frequently Asked Questions about e2e-verify

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

FAQPage Schema
How do I automate Playwright E2E tests before deployment?▼

Automate Playwright E2E tests before deployment by spinning up the dev API server, waiting for port 3000 to respond, and executing the full test suite to surface regressions with root-cause analysis.

What is the best way to find root causes of failed Playwright tests?▼

Finding root causes of failed Playwright tests is handled by running the full test suite against a live dev server and generating a grouped summary report that details Passed, Failed with root cause, and Skipped tests.

Can I run E2E tests against a dev server that starts on port 3000?▼

Yes, you can run E2E tests against a dev server starting on port 3000. The workflow starts the API with npm run dev:api, waits for the server to respond on that port, then executes the Playwright test suite.

How do I check for regressions after making API or UI changes?▼

Check for regressions after API or UI changes by running an automated validation workflow that starts the dev server, executes the full Playwright test suite, and reports grouped failures with structured root-cause analysis.

Does this E2E testing workflow require manual server startup?▼

No, this E2E testing workflow does not require manual server startup. It automatically starts the API server using npm run dev:api and waits for a successful response on port 3000 before executing the Playwright tests.

Related Skills

Explore More Software Engineering Skills→
alasdairncalasdairnc

e2e

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

Community
Advanced
gaashergaasher
150

blue-team

Apply patches to fix code failures from CI/CD test reports and create pull requests.

Community
Advanced
AngelP17AngelP17
1

senior-devops

Automate CI/CD pipelines, infrastructure provisioning, and deployments across AWS, GCP, and Azure.

Community
Intermediate
specvitalspecvital
1

e2e-ui-fix

Fix UI bugs from E2E tests using Playwright MCP verification.

Official
Advanced