On Jul 6, 2011, at 6:19 PM, Eli Barzilay wrote: > 6 minutes ago, John Clements wrote: >> >> In my experience, the one compelling reason not to include unit >> tests in the same module is to trim the 'require' chain for modules >> that are included in the DrRacket startup. > > Yeah -- but much more than just drracket. (And that's in addition to > the discussion on dependencies.) Consider some tests that start some > subprocess that is supposed to help testing -- you wouldn't want that > on normal runs.
Right, yes, that's my point: by putting them in a test suite, you avoid running the tests unless the test suite is explicitly evaluated. Am I misunderstanding you? John
smime.p7s
Description: S/MIME cryptographic signature
_________________________________________________ For list-related administrative tasks: http://lists.racket-lang.org/listinfo/users
