The most elagent solution I've seen to date is simply another project as Michal has suggested. By the OP's definition, these tests span multiple aritfacts/projects and require deployment. Why tie them artifically to a single project and introduce the dependecy problems that come along with that? We have done that in our legacy ant build and it's like quicksand trying to get out of it now. Our build is brittle and slow. A large reason why is we have done just what you propose, keep our integration tests in the same project as our unit tests and production code.
I'd really give the separate project, just for integration/customer tests, some consideration. >>>>> On Wed, 19 May 2004 09:45:51 -0500, Ryan Sonnek <[EMAIL PROTECTED]> said: > 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? > Ryan >> -----Original Message----- From: Maczka Michal >> [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 19, 2004 9:31 >> AM To: 'Maven Users List' Subject: RE: Maven and Integration Test >> >> >> >> >> > -----Original Message----- > From: Amato Massimiliano (TLAB) > >> [mailto:[EMAIL PROTECTED] > Sent: >> Wednesday, May 19, 2004 4:17 PM > To: Maven Users List > Subject: >> Maven and Integration Test >> > >> > >> > Hello, >> > >> > I've a problem with my integration tests. >> > >> > In my system we have both unit and integration test, the > first >> type is perfectly handled by maven that execute them, > and >> generates a report and a clover coverage too. >> > >> > Now I also have integration that are test to cover not the > >> single class but a package and functional tests that must be > run >> on the deployed system that are junit tests aswell. >> > >> > All that comes to my mind is to write and additional goal > that >> must override the test source directory that must be > lauched when >> functional tests wants to be executed, while for > integration i >> think using them as unit test is the best > approach even if they >> are not accounted in the clover report >> > >> > Anyone else ever had a problem like that? What's the solution > >> you implemented? >> > >> Just put them to another project. >> >> Michal >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] For >> additional commands, e-mail: [EMAIL PROTECTED] >> >> > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] For > additional commands, e-mail: [EMAIL PROTECTED] -- ===================================================================== Jeffrey D. Brekke [EMAIL PROTECTED] Wisconsin, USA [EMAIL PROTECTED] [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
