On Sunday 13 January 2008 04:27:38 Ovid wrote:

> --- Salve J Nilsen <[EMAIL PROTECTED]> wrote:

> > 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'?

It doesn't conflate "output TAP results from tests" with "interpret TAP 
results from tests".

-- c

Reply via email to