sh: add new WVPASSRC and WVFAILRC commands.
For testing the value of $?.
sh: Import wvtest.sh from the bup project.
Merge wvtest.py and wvtestmain.py into one file.
This makes it a bit easier to bring into your own projects, since it's just
a single file.
Copied from eqldata project, commit
3b004336b117c01885f09f95b6e2aededd2de377.
Added an initial README.
Rename wvtestrunner to wvtestrun.
Who names their programs as nouns anyway? Clearly it runs things, so it
should be a verb.
Clean up license information and add LICENSE file.
Rename wvtestrunner.pl to wvtestrunner.
The .pl isn't the important part, and someday it might change to another
language. Who knows?
Better 'make clean' targets.
Fix standalone compilation of wvtest/cpp.
Added a Makefile to dotnet as an example of how to run tests.
...and call it from the top level 'make test' too.
Add toplevel and python/ 'make test' example targets.
wvtestrunner: print the time taken by each section, and the total time.
This will perhaps help encourage faster tests.
(cherry picked from commit
6be08f9b861f059da5d3137b7af4e25b77511731)
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!
(cherry picked from commit
9aff60fa6d55a46440a8e4d6bf343753b2bdc1ec)
wvtestrunner: timeouts and CRLF support.
We now time out if there are no test results for 120 seconds. Also handle
surprise CRLFs in the input stream.
(cherry picked from commit
ff9cd2868155ff91201e457008a1bfe0da3e6e40)
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.
(cherry picked from commit
49efbe24c148d69873ca78c05e9c5825d50ef49d)
Import wvtest for python from eqldata project.
Commit
5db96d703ab5a0c253d09d0cbcfd56646eaffbfe.
Import latest wvtest for C#/.NET from versaplex project.
Commit
8f939de8b03b0e0236a182543af0298bb6b97c52.
Import basic C++ wvtest from wvstreams project.
Commit was
333349d03e15b0081c7141f7164bacc2e1fb196a.
Initial .gitignore.