We have nightly builds that mail out build and test results from unit tests and integration tests.
Since there are a small number of developers, we know who did this usually, so nightly tests (and on release to stage/live) are enough, and don't need them every build, unless we specifically want to check what was just done.
Cheers,
Brett
[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.
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
-- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
