For our project, I decided to use a profile and naming convention to include the integration tests. I'm not extremely satisfied with the solution, but it allows us to get cobertura coverage reports from our integrations tests, which was of enough value to us to accept the extra inconvenience.
Parent config:
<project>
...
<build>
<plugins>
...
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-surefire-plugin</artifactId>
<configuration>
<excludes>
<exclude>**/*IntegrationTest.java</exclude>
</excludes>
</configuration>
</plugin>
</plugins>
...
<profiles>
<profile>
<id>integration-test</id>
<build>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-surefire-plugin</artifactId>
<configuration>
<excludes>
<exclude>none</exclude>
</excludes>
</configuration>
</plugin>
</plugins>
</build>
</profile>
</profiles>
</project>
On 4/8/09 12:22 PM, "Jason Voegele" <ja...@jvoegele.com> wrote:
> I'm interested in knowing the current thinking on best practices for
> integration testing in Maven projects. I did find a few articles on the Web
> that discuss this issue, but they all are a bit old now. The most relevant
> article appears to be this one:
>
> http://docs.codehaus.org/display/MAVENUSER/Maven+and+Integration+Testing
>
> "Maven: The Definitive Guide" is curiously silent on this issue.
>
> Can anyone point me to some up-to-date discussion of integration testing best
> practices for Maven? Failing that, would you care to share your thoughts on
> this mailing list?
>
> Thanks.
______________________________
Brian M. Carr
Identity and Access Management
ITS Applications
University of Texas at Austin
V: 512-232-6419
F: 512-471-5746
brianmc...@austin.utexas.edu
smime.p7s
Description: S/MIME cryptographic signature
