1 Configuring the Maven plugin in the pom.xml file
- 1.1 Here is a sample configuration for failsafe with the updated argLine at line 8:

Configuring the Maven plugin in the pom.xml file

The below is handled automatically when using the automatic pom integration (Scanning Builds and Tests using SeaLights Maven plugin - Automatic configuration) with build scanner 2.0.1045 and up

When working with failsafe, you need to update the argLine of failsafe to include the SeaLights test listener and a testStage definition.

Here is a sample configuration for failsafe with the updated argLine at line 8:

<configuration>
</configuration>
  <plugin>
    <groupId>org.apache.maven.plugins</groupId>
    <artifactId>maven-failsafe-plugin</artifactId>
    <version>${maven.failsafe.plugin.version}</version>
    <configuration>
	  <argLine>${argLine} @{sealightsArgLine} -Dsl.testStage="Integration Tests"</argLine>
      <includes>
        <include>**/IT/**/*Test*</include>
      </includes>
    </configuration>
    <executions>
      <execution>
        <goals>
          <goal>integration-test</goal>
          <goal>verify</goal>
        </goals>
      </execution>
    </executions>
  </plugin>

You can set an empty property called sealightsArgLine so that the build will not fail when the SeaLights maven plugin doesn't run

<properties>
  ...
  <sealightsArgLine></sealightsArgLine>
</properties>

Note: As the integration tests usually run against a server, you also need to set it up with the SeaLights test listener as a javaagent

See 'Java Command Reference - Installing test listener as Java Agent' for more parameter values and information

Support

Running integration tests using FailSafe

Analytics

Configuring the Maven plugin in the pom.xml file

Here is a sample configuration for failsafe with the updated argLine at line 8:

Related content