[m-rev.] for review: improve test framework

[Simon Taylor]

On 15-Aug-2002, Zoltan Somogyi <zs at cs.mu.OZ.AU> wrote:
> On 15-Aug-2002, Simon Taylor <stayl at cs.mu.OZ.AU> wrote:
> > In this situation running all the test cases in the directory
> > containing the failing test is also a waste of time. It would
> > be useful to be able to only run the test cases which occur in
> > a specified error log.
> 
> Good idea, though it would be simpler to have a file per directory in
> which "mmake check_local" or some equivalent records the names of the
> failing test cases every time it is run. Or is this file (rather than the
> output of bootcheck or test_mercury) what you meant by "error log"?

`mmake check' leaves a files named "runtests.errs" in the directory
it is invoked in, containing the output from the failed test cases
for the entire run. In the change I'm working on, invoking the
tests using `mmake ERROR_FILE=runtests.errs' will run the failing
tests from runtests.errs in the current directory and its subdirectories.
test_mercury will put this file in the logs directory, so to run the tests
in directory hard_coded which failed on earth last night you would do:

cd tests/hard_coded
mmake ERROR_FILE=/home/mercury/public/test_mercury/logs/test-latest-earth.test_errs runtests

Simon.
--------------------------------------------------------------------------
mercury-reviews mailing list
post:  mercury-reviews at cs.mu.oz.au
administrative address: owner-mercury-reviews at cs.mu.oz.au
unsubscribe: Address: mercury-reviews-request at cs.mu.oz.au Message: unsubscribe
subscribe:   Address: mercury-reviews-request at cs.mu.oz.au Message: subscribe
--------------------------------------------------------------------------