[racket] tests/eli-tester feedback (Was: Racket unit testing)

From: Robby Findler (robby at eecs.northwestern.edu)
Date: Fri Mar 4 06:41:30 EST 2011

FWIW, I don't expect rackunit to change in this particular way (altho
Eli's tester is more like what you're after). There is already a lot
of rackunit code out there and a change like you suggested would break


On Fri, Mar 4, 2011 at 5:29 AM, Neil Van Dyke <neil at neilvandyke.org> wrote:
> Noel Welsh wrote at 03/04/2011 05:54 AM:
>> Since test (suites) are values you can change how you run them. E.g. log
>> the results to disk, or draw pretty graphs.
> This could also be done keeping the test case code imperative, and just
> calling it from a parent context that happens to do the disk-logging or
> graphs.
>> If you check out the code I put on Github, it has broadly the model you're
>> suggesting.
> Thanks, that's encouraging.
> I think I'll wait to see what makes its way into core Racket, and keep using
> my old test stuff in the meantime.
> Neil
> _________________________________________________
>  For list-related administrative tasks:
>  http://lists.racket-lang.org/listinfo/users

Posted on the users mailing list.