[EMAIL PROTECTED] writes:
> You are right about some of my unit test's being more oriented to being
> Integration tests. But regardless of that, some larger projects that have a
> 100's of tests, it still adds up to an appreciable amount of time to run.
> Now, from the tone of the emails, I think everyone agree's that they would
> run all the tests, including the various slower integration tests before
> producing a "deliverable". But often you are not testing a deliverable.
> When i change something small in my web app that then has to be deployed as
> part of a war, adding in the testing time becomes a pain, and (as Henning
> points out) leads to having a larger and larger list of excluded test cases!
I think that many large and small projects have well over 100 tests.
commons-collections has 3560 and builds(with tests) in 53 seconds on
my 800MHz. I do exactly what Henning has showed in the fulcrum build
currently when using Maven which is why I'd like to see different
levels of tests and not a on/off switch.
> A tenet of Agile development is to use what works for you, and discard the
> rest. While I appreciate that Maven faciliates, and even encourages good
> development practices, I don't think it should enforce a set of specific
> practices.
I hear you. I *do* want Maven to promote development best practices.
This is one reason why I like maven, its not just a general build tool
( ala ant ). Same for goes for directory layout arguments.
> It does sound like a lot of people would like to be able to control the
> level of testing. Proposed was a very static "ON/OFF" property. However,
> what would be ideal is to declare various set's of tests, and be able to
> declare which set to run. That way you could declare an empty set, when you
> don't want any tests to run, which is what I think you are proposing as
> well.
I'm not sure about the empty set, but we each can set up our projects as we like.
I do agree it sounds like many like to turn off the tests.
> Having said that, I think the ON/OFF is a quick solution for the short term
> until the more sophisticated solution is found.
If this happens, we should try to make sure that it could never be set
permanently off, at least off would never be the default setting.
I hope I'm not coming off like a hard-nose jerk. If I am I apologize in advance.
jb
--
=====================================================================
Jeffrey D. Brekke [EMAIL PROTECTED]
Wisconsin, USA [EMAIL PROTECTED]
[EMAIL PROTECTED]
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
