This is the mail archive of the
guile@sourceware.cygnus.com
mailing list for the Guile project.
Re: Request for policy: regression tests
- To: Mikael Djurfeldt <djurfeldt at nada dot kth dot se>
- Subject: Re: Request for policy: regression tests
- From: "Greg J. Badros" <gjb at cs dot washington dot edu>
- Date: 17 Dec 1999 08:49:30 -0800
- Cc: bug-guile at gnu dot org, guile at sourceware dot cygnus dot com
- References: <E11yxs4-0004ER-00@mdj.nada.kth.se>
Mikael Djurfeldt <mdj@mdj.nada.kth.se> writes:
> As you know, Jim has written a testsuite found in CVS module
> "guile-modules".
>
> I think we should take as a policy always to run guile-test after
> changes we don't feel we have 100% control over, and not commit things
> if the change doesn't pass the test-suite. [This is not intended as
> criticism. This policy hasn't been stated explicitly for all
> developers.]
>
> Also, lately Jim tried to force all developers always to add a test
> to the suit which exposes the bug when fixing it. This way, we'll
> notice if any change someone makes re-introduces the bug.
>
> With the current CVS version of Guile, guile-test immediately
> generates a segmentation fault on my machine... :(
I suppose I should get cracking on using the test-suite, eh? I didn't
realize it was far enough along to be useful (all I'd done was check it
out). My first guile priority will be restoring proper completion of
the existing test suite.
Greg