On 11 Jan 2008, at 22:19, Ovid wrote:
HARNESS_SKIP_ON_FAIL => Stop the failing test program on first
failure
Remember that neither of those can really stop the test program from
running. The first could halt *subsequent* test programs from running
and the second could merely discard subsequent test results from a
given TAP stream.
I suppose killing the process is a bit draconian / stupid :)
So imagine you have a Web spider with 1000 tests and it fails at the
third test. If the behavior is in the harness, it stops processing
results but the test program keeps running unless you deliberately try
to kill the process. I think it's much cleaner that the thing which
generates the test output knows when to stop.
Good point.
I'm willing to be convinced otherwise, though.
I fear you are correct.
--
Andy Armstrong, Hexten
