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. Robby On Thursday, August 4, 2011, Matthias Felleisen <<a href="mailto:matthias@ccs.neu.edu">matthias@ccs.neu.edu</a>> wrote: > > 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 collection. > 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: > <a href="http://lists.racket-lang.org/listinfo/dev">http://lists.racket-lang.org/listinfo/dev</a> >