e2e-test

Automate end-to-end testing of running microservices via Gateway-first API calls.

Updated Jan 23, 2026
One-click install
npx skills add https://github.com/cooper538/eshop-demo --skill e2e-test-cooper538
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: e2e-test
Source: https://github.com/cooper538/eshop-demo/tree/main/.claude/skills/e2e-test
Command: npx skills add https://github.com/cooper538/eshop-demo --skill e2e-test-cooper538

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill streamlines end-to-end testing for a running microservices deployment, enabling validation of real-world user flows and service interactions without manual instrumentation.

Core Features & Use Cases

  • Gateway-first end-to-end tests: validate the full stack from the API gateway through product, order, notification, and analytics services.
  • Scenario coverage: happy path, unhappy path (out-of-stock, invalid data), order cancellation, and debugging traces.
  • Observability & cleanup: collect logs, traces, and provide guided cleanup of test data and services after runs.

Quick Start

  1. Run discovery to identify running services and health: ./tools/e2e-test/discover.sh
  2. Source environment variables: source ./tools/e2e-test/.env
  3. Execute a scenario, e.g. happy path via Gateway: /e2e-test happy
  4. Inspect results via provided logs and traces; if needed, run trace correlation: ./tools/e2e-test/trace-correlation.sh <correlation-id>

Frequently Asked Questions about e2e-test

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

FAQPage Schema
How do I automate end-to-end tests for running microservices?

Automate end-to-end tests for running microservices by executing scenario workflows against the API gateway to validate full stack interactions. This skill supports interactive and automatic modes to cover happy paths, unhappy paths, and cancellations.

What is gateway-first API testing and when do I need it?

Gateway-first API testing validates the full stack from the API gateway through product, order, notification, and analytics services. You need it to verify real-world user flows and service interactions without manual instrumentation.

How do I run an E2E test scenario and collect logs and traces?

Run an E2E test scenario by sourcing the environment variables and executing the desired scenario command, such as the happy path. Inspect the provided logs and traces, or run trace correlation using a specific correlation ID.

Can I test unhappy paths and order cancellations across microservices?

Yes, you can test unhappy paths and order cancellations across microservices. The skill includes scenario coverage for out-of-stock events, invalid data, and order cancellations to validate service resilience and error handling.

How do I discover running services before executing E2E tests?

Discover running services and check their health by running the provided discovery script. This identifies active microservices in your environment before you source variables and execute the test scenarios.

Does this E2E testing skill provide guided cleanup for test data?

Yes, this E2E testing skill provides guided cleanup of test data and services after runs. It ensures observability by collecting logs and traces while offering structured cleanup to maintain a stable testing environment.