Avery Pennarun [Mon, 24 Nov 2008 22:28:39 +0000 (17:28 -0500)]
wvtestrunner: catch segfaults in the subprogram.
wvtestrunner would notice if the subprogram returned a non-zero exit code,
but not if it died on a signal. Thus, a unit test program dying on a
segfault was considered a success. Oops!
Avery Pennarun [Fri, 1 May 2009 01:02:00 +0000 (21:02 -0400)]
Replaced wvtesthelper/meter/colour scripts with an all-new wvtestrunner.pl.
This one is much smarter than previous versions: by default, it prints out
only the headers from "Testing blah blah:" lines and then prints just a "."
for each "! whatever ok" line. But, if a test does fail, it prints out
*all* the stdout/stderr that was produced by the test from the "Testing blah
blah" line all the way to the failing test.
It also auto-colours ok/FAILED lines, but only if stdout is a tty, so you
don't need to decide whether you want it coloured or not.
Finally, its output is actually compatible with itself: you can run a
top-level wvtestrunner and it'll further summarize the output of inner
wvtestrunners, because the complete output of a given testrunner is in a
single "Testing blah blah:" section. But if a failure occurs, you'll still
get the more detailed results.