On 6/22/06, Marc Dugger <[EMAIL PROTECTED]> wrote:
Here's how I've done it (with help from others from the mailing list):<plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-surefire-plugin</artifactId> <configuration> <skip>false</skip> <includes> <include>**/UnitTestSuite.java</include> </includes> <excludes> <exclude>**/*Test.java</exclude> </excludes> </configuration> <executions> <execution> <id>integration-tests</id> <phase>integration-test</phase> <goals> <goal>test</goal> </goals> <configuration> <skip>false</skip> <forkMode>never</forkMode> <includes> <include>**/IntegrationTestSuite.java</include> </includes> <excludes> <exclude>**/*Test.java</exclude> </excludes> </configuration> </execution> </executions> </plugin> Run 'mvn install' on your project when you want to execute integration tests. Also, I don't separate unit and integration tests by folder.
Marc, How do you double check that all your tests are either in a UnitTestsSuite or an integration one? To solve his particular requirement I would recommend using profiles and then either a separate module or maybe use test class name filtering, perhaps using SomethingTestIT.java and SomethingTest.java to differentiate both types, if he is using JUnit 3. Annotations might be more appropriate with other test frameworks. Cheers, Jerome --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
