Howdy,
When I run prove/TAP::Harness against a Perl test, I can see failures
even when not using verbose mode because, IIRC, that data is sent to
STDERR and ignored by TAP::Harness:
prove t/base.t
t/base....1/316
# Failed test '... And now strict is turned on'
# at t/base.t line 34.
# got: '1'
# expected: '0'
# Looks like you failed 1 test of 316.
t/base.... Dubious, test returned 1 (wstat 256, 0x100)
Failed 1/316 subtests
Test Summary Report
-------------------
t/base (Wstat: 256 Tests: 316 Failed: 1)
Failed test: 17
Non-zero exit status: 1
Files=1, Tests=316, 0 wallclock secs ( 0.05 usr 0.00 sys + 0.09
cusr 0.00 csys = 0.14 CPU)
Result: FAIL
pgTAP, however, has no access to STDERR, so diagnostics and failure
information is sent to STDOUT along with everything else. This means
that if I run tests in non-verbose mode, I don't see any failure
information:
pg_prove -d try sql/index.sql
sql/index.... Failed 1/181 subtests
Test Summary Report
-------------------
sql/index (Wstat: 0 Tests: 181 Failed: 1)
Failed test: 4
Files=1, Tests=181, 1 wallclock secs ( 0.04 usr 0.01 sys + 0.03
cusr 0.03 csys = 0.11 CPU)
Result: FAIL
Of course if I use -v, it passes `verbosity => 1` to TAP::Harness, but
I'd love to be able to see the failure diagnostics without having to
see all of the passing test TAP output, too. Is there some way to get
TAP::Harness to pass through diagnostic output even when `verbosity <
1`? If not, how difficult would it be to add it? Maybe another
parameter to new()?
Thanks,
David
