> -----Original Message----- > From: Tim Stephenson [mailto:[EMAIL PROTECTED] > Sent: Monday, April 26, 2004 1:29 PM > To: '[EMAIL PROTECTED]' > Subject: Query on current approach to integration tests > > > Hi, > > I notice that there have been a few changes to the project xsd (and > supporting implementation classes) around integration tests > sometime over > the last year when I have been away from maven for one reason > or another. > > I have an old problem around how to split out certain tests > (which I dub > 'integration tests') from the regular unit tests. There are 2 ways I > identify these tests: > > a) slow running tests > b) tests that require the project code to be deployed > before testing > begins (eg EJBs) > > I used to employ a modified version of the test plugin that > offered goals > like iutest:test and iutest:single, but unfortunately > developed this when > the test plugin was rapidly evolving so it quickly became > obsolete. Can > anyone suggest the preferred approach to solving this problem > now that the > pom support for the integration source directory is deprecated (and > partially removed) > > Thanks, Tim > The simplest solution is to create one more project for your iu tests. It can either use jar artifact of main project which you want to test or directly operate on sources of the main project. Then you are able to use all goals of test plugin.
Michal --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
