Problem
Every line the tool produces — the [.] / [:] / [+] / [-] progress lines, failure dumps, and errors — is written to os.Stderr. Nothing is ever written to stdout.
Reproduction
$ http-assert --assert-ok http://127.0.0.1:8791/ok 2>/dev/null | wc -c
0
$ http-assert --assert-ok http://127.0.0.1:8791/500 2>/dev/null | wc -c
0
Why it matters
http-assert … > run.log captures an empty file, which is surprising. Standard convention is diagnostics on stderr and results on stdout.
Suggested fix
At minimum document the behaviour. Better: send the pass/fail result and the response dump to stdout, keeping only errors and progress chatter on stderr.
Problem
Every line the tool produces — the
[.]/[:]/[+]/[-]progress lines, failure dumps, and errors — is written toos.Stderr. Nothing is ever written to stdout.Reproduction
Why it matters
http-assert … > run.logcaptures an empty file, which is surprising. Standard convention is diagnostics on stderr and results on stdout.Suggested fix
At minimum document the behaviour. Better: send the pass/fail result and the response dump to stdout, keeping only errors and progress chatter on stderr.