test-all

Run Nexus Gateway end-to-end tests and generate a unified Markdown report.

21|3|Updated May 26, 2026
One-click install
npx skills add https://github.com/AlphaBitCore/nexus-gateway --skill test-all-alphabitcore
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-all
Source: https://github.com/AlphaBitCore/nexus-gateway/tree/main/.claude/skills/test-all
Command: npx skills add https://github.com/AlphaBitCore/nexus-gateway --skill test-all-alphabitcore

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Runs the full Nexus Gateway end-to-end test program (preflight + L1 smoke + L1 Go integration + L2 protocol + L3 AI-judge + L4 Playwright UI) via tests/run-all.sh and surfaces a unified Markdown report. The single "did my change break something" entry point covers ~75 business flows across all five services, each verified by HTTP shape + DB cross-check + Prometheus delta or AI-judge verdict. Trigger keywords: test all, run regression, smoke everything, full regression, e2e tests, regression sweep, /test-all. No required inputs; reads tests/.env.local for VKs and admin credentials. Output: a Markdown report at /tmp/nexus-test/test-all-<UTC-timestamp>.md plus a fan-out summary in this conversation.

Core Features & Use Cases

  • One-command end-to-end test harness that triggers preflight and multiple phases across services.
  • Generates a Markdown test report at /tmp/nexus-test/test-all-<UTC-timestamp>.md and a per-phase status summary.
  • Supports flags for quick/full/phase selection and preflight control.
  • Validates prerequisites (VKs and running services) before execution and surfaces actionable gaps.
  • Ideal before PRs or after significant changes to validate end-to-end integrity.

Quick Start

Run the tests from repo root with bash tests/run-all.sh.

Frequently Asked Questions about test-all

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

FAQPage Schema
How do I run end-to-end regression tests for Nexus Gateway services?

Run end-to-end regression tests for Nexus Gateway by executing `bash tests/run-all.sh` from the repository root to automate preflight, L1 smoke, L1 Go integration, L2 protocol, L3 AI-judge, and L4 Playwright UI test phases.

What is included in the Nexus Gateway full regression sweep?

A full regression sweep covers approximately 75 business flows across five services, verified by HTTP shape, database cross-checks, Prometheus deltas, or AI-judge verdicts, producing a unified Markdown report.

Do I need to configure credentials before running Nexus Gateway e2e tests?

Yes, you need to configure credentials before running Nexus Gateway e2e tests by placing VKs and admin credentials in the `tests/.env.local` file, as the test harness reads this file to validate prerequisites.

Where does the automated end-to-end test report get saved?

The automated end-to-end test report is saved as a Markdown file at `/tmp/nexus-test/test-all-<UTC-timestamp>.md`, alongside a per-phase status summary fanned out directly in the conversation.

Can I run a quick smoke test instead of the full Nexus Gateway test suite?

Yes, you can run a quick smoke test instead of the full suite by using supported flags for quick, full, or phase selection and preflight control when triggering the `tests/run-all.sh` script.

Why should I run an e2e regression sweep before submitting a pull request?

Running an e2e regression sweep before a pull request validates end-to-end integrity across all services, confirming whether your significant changes broke any of the 75 covered business flows.