Skip to content

/e2e-suite

Testing class

Writes test source into the repo and executes it — the only class that does both. Shared rules: CONVENTIONS-testing.md.

Umbrella over the testing class: /e2e-run captures evidence, /test-triage classifies it, /flake-watch supplies history, /test-report writes the matrix. Aggregates one PASS / WARN / BLOCK and honours the CI exit-code contract. Never repairs anything.

At a glance

Run it /e2e-suite
Class testing
Version 0.1.0
Author navjyotnishant
Cost one run plus per-failure triage, fanned out under a concurrency cap — cost scales with the number of failures, not the size of the suite
Needs nj-run (this toolkit, bin/) · /e2e-run · /test-triage · /flake-watch + the ledger · /test-report
Source skills/e2e-suite/SKILL.md

What it needs, and what happens without it

Every tool is detected at runtime — none is installed for you.

Tool Without it
nj-run (this toolkit, bin/) aggregate by hand per Step 4's table; say cost and subagent records are missing
/e2e-run BLOCK — nothing to aggregate
/test-triage report raw failures, verdict WARN, and say classification was unavailable
/flake-watch + the ledger triage runs without the flake class; say so
/test-report report without it, and say so

Agents it spawns

  • failure-triager — Classify ONE e2e test failure as real defect, test bug, environment, flake, or data — each with a confidence…

The procedure

The executable steps live in the skill file itself and are deliberately not reproduced here: they are instructions to the model at runtime, not documentation.

Read e2e-suite/SKILL.md →