Hi Kenney, > -----Original Message----- > From: Kenney Westerhof (JIRA) [mailto:[EMAIL PROTECTED] > Sent: jeudi 14 juillet 2005 22:33 > To: [email protected] > Subject: [jira] Created: (MNG-591) Integration tests lifecycle
[snip] > [Btw, I'm doing this while creating a cactus plugin, for the moment using > cargo in the TestSuite itself to deploy.] Cool :-) > The idea is that the integration test sources go in src/itest/*; Don't you mean src/test/itest/*? I think I'd prefer src/test/cactus actually because there can possibly be different types of integration tests for the same project and each would need to be run with its own testing framework (which might not be junit BTW). [snip] > that > there be a integration-test-compile, > integration-test-package and/or integration-test-appdeploy[or something] > and that surefire > is also bound to integration-test. I'm not sure about the surefire thing. Again when it comes to integration testing there can be several test frameworks. I think it should be left to the different integration test plugins to add themselves to the lifecycle. Of course the surefire plugin could possibly also be an integration test plugin and add itself to the integration test phases but it shouldn't be considered the only one I think. > Maybe something can be done using the src/test/project/some-project/.... > approach seen in > maven-javadoc-plugin, maven-site-plugin and maven-eclipse-plugin (i'd like > to see some of that > standardized anyway to allow plugin testing generally - which can also be > seen as integration testing). For plugin testing, we have had a discussion thread on that on the list. We agreed that the way forward would be to have a helper class (and possibly a plugin later on if required) to embed a m2 instance in the test. -Vincent --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
