On 7/27/06, Chris Wall <[EMAIL PROTECTED]> wrote:
I would like to turn off maven-surefire-plugin during the "test" phase (so, no unit testing at all), and turn on maven-surefire-plugin for the "integration-test". Basically my source is a test webapp, and my tests are integration tests.
The usual advice is to put your integration tests in a separate module, and bind executions of the compiler and surefire to the right phases. Here's an example of that: http://svn.apache.org/repos/asf/struts/struts1/trunk/integration/apps-it/pom.xml (There are much better examples in the Better Builds with Maven book from Mergere.) Check the archives for some of my recent posts (2-3 months). I got some help configuring the Shale Framework examples webapps, where we needed to keep the integration tests in the same module as the example app and its unit tests. Here's one of those poms: http://svn.apache.org/repos/asf/shale/framework/trunk/shale-apps/shale-blank/pom.xml Along those lines, for your project, try letting Surefire run during 'test', but excluding all of the test classes. Then bind a second execution of surefire to the integration-test phase. (Based on the Shale example, you might have to explicitly <include> the test classes.) HTH, -- Wendy --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
