[racket-dev] testing

From: Robby Findler (robby at eecs.northwestern.edu)
Date: Thu Aug 4 12:55:52 EDT 2011

I think that we can accommodate all of that by simply standardizing a place
where an entire test can be run from. That is, I expect the interesting
question this answers is "I have just food and fixed a bug in some unknown
code: where do I go to find the relevant tests to add more and run all the
existing ones?". All that is required for that is some place to start
looking; from there DrRacket can help you find everything.


On Thursday, August 4, 2011, Matthias Felleisen <matthias at ccs.neu.edu>
> On Aug 4, 2011, at 12:19 PM, Vincent St-Amour wrote:
>> The above suggestion does not rule out individual testing styles. It
>> only mentions a standardized entry point. What the test suite does
>> afterwards can still be left to the programmer.
> I really really prefer placing my tests in a directory within the
> Perhaps it is the proximity perhaps the not-thinking-about-where.
> Indeed, for plain unit tests, I prefer to place them inside the module.
> That's what I mean personal testing style.
> _________________________________________________
>  For list-related administrative tasks:
>  http://lists.racket-lang.org/listinfo/dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.racket-lang.org/dev/archive/attachments/20110804/892d3cf2/attachment.html>

Posted on the dev mailing list.