run-e2e

Run Playwright end-to-end tests with automated API server lifecycle management.

1|Updated Jan 16, 2026
One-click install
npx skills add https://github.com/WhatIfWeDigDeeper/application-tracker --skill run-e2e-whatifwedigdeeper
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: run-e2e
Source: https://github.com/WhatIfWeDigDeeper/application-tracker/tree/main/.claude/skills/run-e2e
Command: npx skills add https://github.com/WhatIfWeDigDeeper/application-tracker --skill run-e2e-whatifwedigdeeper

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill streamlines the process of running end-to-end tests by automatically managing the lifecycle of API servers, ensuring they are running when needed and cleaned up afterward.

Core Features & Use Cases

  • Automated API Server Management: Starts API servers for specified stacks if they are not already running.
  • Selective or Full Stack Testing: Allows running tests for a single stack or all stacks in the project.
  • Cleanup: Stops only the API servers that were started by the script.
  • Use Case: When developing a new feature, you can use this Skill to quickly run all end-to-end tests across different technology stacks without manually starting and stopping each backend server.

Quick Start

Run end-to-end tests for all stacks in the project.

Frequently Asked Questions about run-e2e

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

FAQPage Schema
How do I run Playwright e2e tests across multiple stacks without manually starting backend servers?

Running Playwright e2e tests across multiple stacks is handled by automating API server lifecycle management. The script starts necessary backend services before test execution and shuts them down automatically afterward.

How does automated API server lifecycle management work during end-to-end testing?

Automated API server lifecycle management works by detecting inactive backend services for specified stacks, starting them via bash scripting, and terminating only the servers instantiated by the script post-testing.

Can I run e2e tests for a single stack instead of all stacks in the project?

You can run e2e tests for a single stack or all stacks in the project. The script allows selective targeting of individual application stacks while managing the required API servers.

Why are my API servers staying open after my e2e tests finish?

API servers should shut down automatically after e2e tests finish. The script stops only the API servers it started, leaving any previously active backend services running.

How do I debug API startup failures during automated end-to-end testing?

Debug API startup failures during automated e2e testing using generated log files. The script integrates bash scripting for deterministic task execution and produces logs specifically for troubleshooting API initialization issues.