e2e-test-runner

Validates end-to-end user journeys, smoke tests, and synthetic probes across app surfaces.

Updated Dec 24, 2025
One-click install
npx skills add https://github.com/JoyJoin-Tech-Limited/JoyJoin_app_v0.1 --skill e2e-test-runner-joyjoin-tech-limited
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: e2e-test-runner
Source: https://github.com/JoyJoin-Tech-Limited/JoyJoin_app_v0.1/tree/main/.github/skills/e2e-test-runner
Command: npx skills add https://github.com/JoyJoin-Tech-Limited/JoyJoin_app_v0.1 --skill e2e-test-runner-joyjoin-tech-limited

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Verifying that a full user journey actually works across API and client layers is hard when repo scripts are stale, coverage gaps are hidden, and environment assumptions go undocumented. This Skill provides a disciplined approach to flow-level verification so you test active product flows rather than outdated scripts. ## Core Features & Use Cases - Journey-Level Validation: Run or design end-to-end flow tests, smoke tests, and synthetic probes that verify users can complete flows, not just that individual requests return 200. - Harness Selection Guidance: Match the right tool to the goal, from the lightweight happy-path-probe.mjs production probe to Playwright MCP for browser journeys and WeChat DevTools MCP for mini-program flows. - Stale Script Detection: Identify scripts like test-e2e-flow.ts that target deprecated flows and treat them as migration candidates instead of proof of coverage. - Use Case: After a risky deployment, use this Skill to define the shortest realistic journey that proves the affected flow still works, run the synthetic probe via workflow_dispatch, and document environment assumptions. ## Quick Start Ask the AI to run an end-to-end smoke test of the signup flow and report any coverage gaps in the existing E2E scripts.

Frequently Asked Questions about e2e-test-runner

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

FAQPage Schema
How do I run an end-to-end smoke test after a deployment?▼

Run the synthetic probe script `scripts/synthetic/happy-path-probe.mjs` or trigger it via `workflow_dispatch` on the synthetic-probe workflow to validate health, metrics, and auth responses. For broader coverage, define the shortest realistic user journey that exercises the changed flow.

What is the difference between a synthetic probe and a full E2E test?▼

A synthetic probe is a lightweight availability check that confirms a service is healthy, while a full E2E test validates a complete multi-step user journey across API and client layers. A passing probe does not guarantee the user flow works.

Can I use Playwright to test browser user journeys?▼

Yes, the Playwright MCP server can navigate routes, interact with forms, and capture screenshots against the live admin-client web surface. This verifies critical paths without writing a full test script.

Why does an existing E2E script test the wrong flow?▼

Some repo scripts are stale; for example, `test-e2e-flow.ts` targets a deprecated V2 personality flow. Treat such scripts as migration candidates and use active product flows as the source of truth instead.

When should I not use flow-level E2E testing?▼

Avoid it for unit, invariant, or structural regression tests, which belong in lower-level test suites. It is also the wrong tool for frontend loading or transition performance questions rather than functional journey correctness.