> -----Original Message-----
> From: Ryan Sonnek [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, May 19, 2004 4:46 PM
> To: Maven Users List
> Subject: RE: Maven and Integration Test
>
>
> I was REALLY hoping to hear another solution to this problem.
> I'm running into the same thing, and would like to contain
> my project code (tests and all). I remember the cactus
> plugin introducing the concept of src/test-cactus for it's
> integration test code.
>
> Two options would be to reuse the current test plugin and
> change the source directory dynamically, or create another
> "test" plugin for integration tests that looks to something
> like src/test-integration. I think that creating a new test
> plugin might make the most sence in order to plug easier into
> project reports. How plausible is this?
>
I think it's the bad idea. You can have quite a few types of integration
tests.
/src/test
/test-cactus
/test-stresstests
/test-db
and so on. It makes it difficult to maintain, difficult to select which type
of tests you want
to execute and difficult to integrate with plugins like idea, eclipse and so
on.
the layout:
mainproject
/src
/test
java
....(unit tests)
mainproject-iu-catus
/src
/test
java
....
mainproject-iu-stresstests
mainproject-iu-test-db
is scalable and it will work out of the box with existing test plugin and is
supported by idea/eclipse plugins.
Michal
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
