[plt-scheme] Best way to run a bunch of test-suites with schemeunit?

From: Robby Findler (robby at cs.uchicago.edu)
Date: Sun Jun 17 14:16:52 EDT 2007

I'm not quite sure that's what I asked for, did I? I thought I was
just asking for an easier way to get started with a test suite and
better ways to add stuff to the test suite, but only as it was needed.
(Currently, lots of boilerplate is required, imo).


On 6/17/07, Noel Welsh <noelwelsh at gmail.com> wrote:
> On 6/17/07, Grant Rettke <grettke at acm.org> wrote:
> >
> > How would I go about running each test case for each test file in a
> > single pass at the console?
> >
> Ryan has told you how to combine test cases and suites into larger
> suites.  I normally have a file called 'run-tests.ss' that contains
> something like the following:
> (require (planet "test.ss" ("schematics" "schemeunit.plt" 2)))
> (require (planet "text-ui.ss" ("schematics" "schemeunit.plt" 2)))
> (require "all-vb-tests.ss")
> (test/text-ui all-vb-tests)
> On the console I use the following command:
> mzscheme -qev '(exit (load "run-tests.ss"))'
> -----------
> Aside: Various people (not naming names, but Robby) have requested a
> feature that would automatically collect test cases into a default
> test suite and automatically run them.  I've implemented a hacky
> version of this, but to work properly it should transparently work
> with all shortcuts.  Till recently I couldn't figure out how to do
> this, but I recently had the thought that I could abuse #%module-begin
> to set a parameter that has module level scope.  So it will happen
> when I feel the impetus to implement it, and will mean you have to
> write less code to construct test suites, at the cost of having less
> flexibility over how tests are run.
> N.
> _________________________________________________
>   For list-related administrative tasks:
>   http://list.cs.brown.edu/mailman/listinfo/plt-scheme

Posted on the users mailing list.