From 7cb1a8e81cb6e0dff84524ff378361086be11dfe Mon Sep 17 00:00:00 2001 From: grokbot_ty Date: Mon, 7 Sep 2026 04:41:36 +0000 Subject: [PATCH] docs: add Results recording & report-out section to TEST-SPEC --- docs/TEST-SPEC.md | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/docs/TEST-SPEC.md b/docs/TEST-SPEC.md index 46b6aa5..f6336b3 100644 --- a/docs/TEST-SPEC.md +++ b/docs/TEST-SPEC.md @@ -64,6 +64,18 @@ Test dependencies are pinned in `backend/tests/requirements-test.txt` and `front --- +## Results recording & report-out + +Every report maps to named case IDs from this spec. Allowed results only: `pass`, `fail`, `not run`, and optionally `blocked` with a blocker pointer. Never invent pass. + +Evidence is required for every `pass` or `fail`: a path or paste of real runner output (pytest, httpx, compose logs, curl). No evidence → `not run`. Report table columns are: case id · result · evidence pointer · blocker (if fail). + +The Test Bar may only summarize what runners printed. Ty also reads raw results and owns gate exit. Gate or phase exit evidence in the Gates section still requires Ty confirmation where IMPL-PLAN mandates it — bots never declare Gate B or Gate C green. + +When code does not exist yet, Phase 0 and earlier cases stay `not run`. Do not speculate. + +--- + ## 3. Test pyramid overview Each row states the test layer, when tests in that layer are written, and what document drives the expected behavior.