You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
feat(core): report inconclusive status when all tests have execution errors (#941)
* feat(core): report inconclusive status when all tests have execution errors
When all eval tests fail due to execution errors (e.g., misconfigured
model, network failures), the run now reports INCONCLUSIVE instead of
a misleading PASS/FAIL verdict.
- Exit code 2 for all-execution-error runs (distinct from exit 1 for
threshold failures)
- CLI shows yellow INCONCLUSIVE verdict with clear messaging
- JUnit XML uses executionStatus to classify <error> vs <failure>,
preventing double-counting of execution errors as failures
Closes#894
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
* docs: clarify manual red/green UAT as blocking step in E2E checklist
Make the UAT requirement more prominent with a blocking warning,
clearer red/green definitions, and explicit dependency on completing
UAT before proceeding to later checklist steps.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Copy file name to clipboardExpand all lines: AGENTS.md
+7-6Lines changed: 7 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -266,17 +266,18 @@ Before marking any branch as ready for review, complete this checklist:
266
266
267
267
2.**Run unit tests**: `bun run test` — all must pass.
268
268
269
-
3.**Manual red/green UAT (REQUIRED for all changes):**
270
-
Automated tests are not sufficient. Every change must be manually verified from the end user's perspective using a red/green approach:
271
-
-**Red (before fix):** Reproduce the bug or demonstrate the missing feature on `main` (or before your change). Confirm the undesired behavior is observable from the CLI / user-facing output.
272
-
-**Green (after fix):** Run the same scenario with your changes applied. Confirm the fix or feature works correctly from the end user's perspective.
273
-
- Document both the red and green results in the PR or conversation so the user can see the before/after.
269
+
3.**⚠️ BLOCKING: Manual red/green UAT — must complete before steps 4-5:**
270
+
Unit tests passing is NOT sufficient. Every change must be manually verified from the end user's perspective. Do NOT skip this step or proceed to step 4 until red/green evidence is documented.
271
+
272
+
-**Red (before your changes):** Run the scenario on `main` (or the code state before your changes). Confirm the bug or missing feature is observable from the CLI / user-facing output. Capture the output.
273
+
-**Green (with your changes):** Run the identical scenario with your branch. Confirm the fix or feature works correctly from the end user's perspective. Capture the output.
274
+
-**Document both** red and green results in the PR description or comments so reviewers can see the before/after evidence.
274
275
275
276
For evaluator changes, this means running a real eval (not `--dry-run`) and inspecting the output JSONL. For CLI/UX changes, this means running the CLI command and verifying the console output.
276
277
277
278
4.**Verify no regressions** in areas adjacent to your changes (e.g., if you changed evaluator parsing, run an eval that exercises different evaluator types).
278
279
279
-
5.**Mark PR as ready** only after all above steps pass.
280
+
5.**Mark PR as ready** only after steps 1-4 have been completed AND red/green UAT evidence is included in the PR.
0 commit comments