Ovid said:
--- Salve J Nilsen <[EMAIL PROTECTED]> wrote:
Ok, a shot in the dark...
1. Redirect test output to a temporary log file (which should get
cleaned up during "make clean" &al.)
2. Let the harness be "aware" of this log file, and "tail(1)" it as
things get written to it, printing whatever's relevant/asked for to
the terminal.
3. If there's an error detected, write a warning at the end of the
test run, pointing to the log file (and perhaps line number in it.)
How is this simpler than 'bail on fail' or 'die on fail'?
Perhaps it's not easier to implement, no. But the user gets at least
access to the entire set of errors and warnings while still getting the
high-level test report in the terminal.
If the goal here is to reduce the amount of "pointless" tests run because
of some failure in an earlier test (DIE_ON_FAILURE=1), then this
suggestion may be a bit off the mark. But if the goal is to get access to
the first failing diagnostics, then just keeping them around in a file
ought to be enough (and that would also give you the option to do
something with the test output you might not otherwise, e.g. post-test
analysis or statistics gathering.)
- Salve
--
#!/usr/bin/perl
sub AUTOLOAD{$AUTOLOAD=~/.*::(\d+)/;seek(DATA,$1,0);print# Salve Joshua Nilsen
getc DATA}$"="'};&{'";@_=unpack("C*",unpack("u*",':4@,$'.# <[EMAIL
PROTECTED]>
'2!--"5-(50P%$PL,!0X354UC-PP%/0\`'."\n"));eval "&{'@_'}"; __END__ is near! :)
