feat: --junit on suite run + prove — CI-native JUnit XML, fail-closed#40
Merged
Conversation
Both commands also write a JUnit XML report for standard CI test-widget ingestion, mirroring each command's existing grouping: one <testsuite> per dimension (suite run) or per evidence lane (prove), one <testcase> per test or lane. A scored FAIL is a <failure> carrying the measured reason; an INCONCLUSIVE dimension, a SIMULATOR_INVALID run, or a refused/inconclusive lane is an <error> with the refusal reason preserved -- never a <failure>, never a silent pass. No timestamp attribute; a repeat run renders byte-identical XML. Claude-Session: https://claude.ai/code/session_015njkxtoAKioqTPT2k14xFr
… entry 'a real, drift-checked flow' -> 'a drift-checked flow': the flow's drift-check is the fact; vouching for realness adds nothing. Claude-Session: https://claude.ai/code/session_015njkxtoAKioqTPT2k14xFr
hotato turn-taking eval8 of 8 scenarios pass. 0 fail. No regression.
RegressionsNone. Reproducible timing measured locally from call audio. Swap the bundled self-test step for your own captured recordings to gate on your agent. github.com/attenlabs/hotato |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Answers the most-thumbed CI-native ask in the eval-tool space (JUnit/XML report output; promptfoo #9071 pattern) with hotato's semantics kept intact:
--junit PATHon bothhotato suite runandhotato prove<testsuite>per dimension (suite run) / evidence lane (prove); one<testcase>per test or lane<failure>with the measured reason<error>, never<failure>, never silent green — plus a suite-verdict<error>backstop so the XML can never read green while the exit code gatesIndependently verified on-branch by a fresh reviewer: mapping confirmed with its own constructed cases (incl. hostile-character escaping and root-count consistency), byte-stable across runs, and
git diffremoves zero lines from any fail-closed path. Also strips one authenticity-protest phrase from the candidate CHANGELOG entry per house copy rules.https://claude.ai/code/session_015njkxtoAKioqTPT2k14xFr