How to use Maven Surefire plug-in with different groups for test and integration-test?

Question

I want to use testng with the Surefire plug-in of Maven. The idea is to tag some tests with a group integrationTest and run the plug-in twice: for goal test excluding the group integrationTest and for goal integration-test including the group integrationTest only.

I found some material for running the plug-in for both goals and that works, but the group for the second run does not work (no test is executed).

Here is the plug-in configuration in the build element of my pom.xml:

  <plugin>
    <artifactId>maven-surefire-plugin</artifactId>
    <configuration>
      <excludedGroups>integrationTest</excludedGroups>
      <reportFormat>brief</reportFormat>
      <trimStackTrace>true</trimStackTrace>
      <useFile>false</useFile>
    </configuration>
    <executions>
      <execution>
        <id>integration-test</id>
        <phase>integration-test</phase>
        <goals>
          <goal>test</goal>
        </goals>
        <configuration>
          <groups>integrationTest</groups>
          <excludedGroups/>
          <reportsDirectory>${project.build.directory}/surefire-reports/integration</reportsDirectory>
        </configuration>
      </execution>
    </executions>
  </plugin>

Any idea? mvn integration-test runs all unit tests as expected (excluding the group integrationTest) but the second test run just writes:

Running TestSuite
Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.562 sec

The Result of mvn test is as expected, tests run and group integrationTest is ignored.

Answer 1

I got it - irritating configuration implementation!

<excludedGroups/> does not override <excludedGroups>integrationTest</excludedGroups>. You need to specify any (unknown) group instead, <excludedGroups>none</excludedGroups> for example.

Answer 2

The Failsafe plugin is the best way to do this (it may not have been available when you posted this question). It adds an integration-test phase to the build lifecycle. It allows you to have setup and teardown activities run before and after the tests, which is useful for managing an embedded container, for example.