Tests pin down chain ordering (including ties), BaseAdvisor stream behaviour, redaction order versus memory and logging, the tool loop, and how a refusal surfaces on calls, streams and over HTTP. Co-Authored-By: Claude Sonnet 5 <[email protected]> Claude-Session: https://claude.ai/code/session_01Ja4jkzrbQ4LQZBNrb5mkZE
10 lines
417 B
Bash
Executable File
10 lines
417 B
Bash
Executable File
#!/usr/bin/env bash
|
|
# Regenerates every file under output/ (01-21). The test suite writes all of them itself through
|
|
# the Transcript helper. No database, no Docker and no API key is needed: the "model" is a
|
|
# recording stub, so what the tests prove is what reached it and what came back.
|
|
set -euo pipefail
|
|
cd "$(dirname "$0")/.."
|
|
rm -rf target
|
|
mvn -q -B test 2>&1 | grep -E "Tests run:|BUILD|FAIL" || true
|
|
ls output
|