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

Fergus Henderson fjh at cs.mu.OZ.AU
Thu Aug 15 19:22:24 AEST 2002


On 15-Aug-2002, Mark Brown <dougl at cs.mu.OZ.AU> wrote:
> 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:
> > > +# SUBDIRS - the names of any subdirectories containing tests.
> > 
> > In think one of the problems with the current system is that you can't run the
> > tests in e.g. the hard_coded directory without also running the tests in the
> > hard_coded/exceptions, hard_coded/purity, hard_coded/sub-modules and
> > hard_coded/typeclasses directories.
> 
> You also can't easily run a subset of the test cases in the hard_coded
> directory without running all of them.

Actually, you can.

	mmake foo.res bar.res

> But the question is: why would you want to?

I do this all the time, for exactly the reason that Zoltan described.

> Is it just a case of sacrificing stability in order to speed development,

No.  It is a case of running the tests in the right order in order
to speed development by getting quick notification of the most likely
failures.  No stability is sacrificed so long as you run a full
bootcheck before committing.

-- 
Fergus Henderson <fjh at cs.mu.oz.au>  |  "I have always known that the pursuit
The University of Melbourne         |  of excellence is a lethal habit"
WWW: <http://www.cs.mu.oz.au/~fjh>  |     -- the last words of T. S. Garp.
--------------------------------------------------------------------------
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
--------------------------------------------------------------------------



More information about the reviews mailing list