tests in Maven2

[Brett Porter <br...@apache.org>]

Hi,

Just examining the lifecycle and looking at some comments on the users 
list about testing, and wondering if we might need to adapt the 
lifecycle a bit better to different types of tests.

Currently, we have "test" which exists before package, and has its own 
source code and resources, but its classes are not processed like a 
normal build. Then we have integration-test and verify which occur after 
packaging, but before installation, and don't have any sources of their own.

We are also missing the case where you might have intensive tests that 
you don't want to run during development. I still think these belong 
before install, and can be enabled in an integration environment using 
profiles instead.

integration-test might also be a bad name as we seem to be using it for 
funtional testing as well.

Can we think of better ways to specify test sets than this?

What I'm thinking is:
- we have unit-test, functional-test (both before package), and 
integration-test
- each has an identical lifecycle to main 
(generate/process-sources/resources, process-classes)
- it is up to the user to use profiles to apply things they want in dev 
or not

I'll probably get told integration tests should go in separate projects. 
That is a possibility, however, I don't think we should have to rely on 
it being installed before it is tested. Maybe that's not a big deal, 
esp. since the reactor should be able to take care of it, however I feel 
there is some merit to keeping it all together, especially as IDEs might 
deal with it better that way if they have plugins for the testing 
framework. Of course it is still possible to have a separate test suite, 
using dependencies to get the code to test.

Thoughts?

- Brett

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org