On Wednesday 22 January 2003 2:19 pm, [EMAIL PROTECTED] wrote: > I agree the off should NOT be the default. Maven should encourage good > practices, just not mandate them. Also, I think that projects like > commons-collections have many test that run quickly because they don't have > slow aspects like lots of filesystem access or testing parsing 1000 MB > files, or interfacing with databases. But many business specific code does > that type of thing, versus more general libraries. >
IMHO what you mention above are not unit tests. A Unit test should only test one class. I know it is difficult to test classes that use databases and sockets etc but either mockobjects should be used or move these sort of tests out into an intgration test. Here we use a testharness package that is in src/java. This seems to work OK but is not ideal. > It sounds like consensus is that different levels would be the best, > especially if you can still perform an on/off switch setup! > > Eric Pugh > > cheers bill -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
