e2e-test

Validates web applications by executing end-to-end user journeys in browsers and via HTTP APIs.

Updated May 3, 2026
One-click install
npx skills add https://github.com/spikelab/multiplai-cc-mktplace --skill e2e-test-spikelab
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: e2e-test
Source: https://github.com/spikelab/multiplai-cc-mktplace/tree/main/plugins/multiplai-dev/skills/e2e-test
Command: npx skills add https://github.com/spikelab/multiplai-cc-mktplace --skill e2e-test-spikelab

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Unit tests passing does not prove an application actually works for users. This Skill validates real user journeys end-to-end — in a browser for frontends and over HTTP for backend APIs — catching broken flows, contract mismatches, and data-layer issues before release. ## Core Features & Use Cases - Dual testing modes: Frontend mode drives a browser via agent-browser; backend mode exercises APIs with curl, with auto-detection of which mode fits the codebase. - Spec-aware test planning: Reads OpenSpec requirements as ground truth for what to test, falling back to codebase route and auth discovery when specs are absent. - Self-healing journeys: Each journey runs in a dedicated sub-agent that retries failed steps up to 3 times, fixes critical blockers, and documents remaining issues. - Use Case: After finishing a feature build, run the skill against your local dev server to verify registration, login, and CRUD flows actually work, then receive a structured markdown report with pass/fail status, screenshots, and DB verification results. ## Quick Start Ask the agent to run end-to-end tests against your app, for example: "Run e2e tests on my app at localhost:3000 and export the report to e2e-report.md."

Frequently Asked Questions about e2e-test

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

FAQPage Schema
How do I run end-to-end tests on a web application?

Invoke the skill with an optional base URL and mode flag. It auto-detects frontend versus backend stacks, starts the dev server if needed, discovers routes and auth, then executes user journeys and produces a structured pass/fail report.

How to test a backend API end to end with curl?

Use backend mode, which exercises API journeys over HTTP with curl: happy-path requests, error cases like 400/401/404, auth token lifecycles, and response contract checks. Results include status codes, body validation, and DB verification.

Does frontend e2e testing require a browser automation tool?

Yes, frontend mode requires the agent-browser CLI to be installed. If it is unavailable, the skill reports this and falls back to backend-only testing rather than auto-installing anything.

Can e2e tests use OpenSpec requirements as the test plan?

Yes. When OpenSpec requirement artifacts exist under specs/changes, they are treated as ground truth and mapped to test journeys. Without specs, the skill falls back to discovering routes, auth, and data models from the codebase.

What are the limitations of this e2e testing approach?

Journeys run sequentially to avoid state conflicts, self-healing is capped at 3 attempts per step, DB verification needs direct database access tools, and screenshots are for debugging only with no visual regression comparison.