Improve structure of integration tests
Issue #38
closed
Move to special naming convention of integration tests. This improvement help us to remove skipAllTests=true
Comments (5)
-
-
reporter <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-failsafe-plugin</artifactId> <version>${failsafe.plugin.version}</version> <executions> <execution> <goals> <goal>integration-test</goal> <goal>verify</goal> </goals> </execution> </executions> </plugin>
-
reporter - changed status to open
-
reporter We can execute integration tests with
maven-surefire-plugin
withoutfailsafe
plugin:<executions> <execution> <id>default-test</id> <phase>test</phase> <configuration> <skip>true</skip> </configuration> </execution> <execution> <id>integration-test</id> <phase>pre-site</phase> <goals> <goal>test</goal> </goals> </execution> </executions>
-
reporter - changed status to closed
Closes
#38→ <<cset e230b362883c>>
- Log in to comment
Main page - how to run intergration tests with surefire: http://maven.apache.org/surefire/maven-failsafe-plugin/integration-test-mojo.html About naming convention: http://maven.apache.org/surefire/maven-failsafe-plugin/examples/inclusion-exclusion.html
Pay your attention on the following lines:
By default, the Failsafe Plugin will automatically include all test classes with the following wildcard patterns:
"/IT*.java" - includes all of its subdirectories and all Java filenames that start with "IT". "/IT.java" - includes all of its subdirectories and all Java filenames that end with "IT". "/ITCase.java" - includes all of its subdirectories and all Java filenames that end with "ITCase".