Built by Maven

tycho-surefire:verify

Full name:

org.eclipse.tycho:tycho-surefire-plugin:4.0.0:verify

Description:

Verifies plugin-test runs from the integration-test stage

Attributes:

  • Requires a Maven project to be executed.
  • The goal is thread-safe and supports parallel builds.
  • Binds by default to the lifecycle phase: verify.

Required Parameters

Name Type Since Description
<summaryFile> File - The summary file to read integration test results from.
Default value is: ${project.build.directory}/failsafe-reports/failsafe-summary.xml.

Optional Parameters

Name Type Since Description
<basedir> File - The base directory of the project being tested. This can be obtained in your unit test by System.getProperty("basedir").
Default value is: ${basedir}.
<encoding> String - Deprecated. The character encoding scheme to be applied. Deprecated since 2.20.1 and used encoding UTF-8 in failsafe-summary.xml.
Default value is: ${project.reporting.outputEncoding}.
User property is: encoding.
<failIfNoTests> boolean 2.4 Set this to "true" to cause a failure if there are no tests to run. Defaults to "false".
Default value is: false.
User property is: failIfNoTests.
<failOnFlakeCount> int 3.0.0-M6 Set this to a value greater than 0 to fail the whole test set if the cumulative number of flakes reaches this threshold. Set to 0 to allow an unlimited number of flakes.
Default value is: 0.
User property is: failsafe.failOnFlakeCount.
<packaging> String - (no description)
Default value is: eclipse-plugin.
User property is: tycho.verify-test.packaging.
<reportsDirectory> File - Base directory where all reports are written to.
Default value is: ${project.build.directory}/failsafe-reports.
<skip> boolean - Set this to 'true' to bypass unit tests entirely. Its use is NOT RECOMMENDED, especially if you enable it using the "maven.test.skip" property, because maven.test.skip disables both running the tests and compiling the tests. Consider using the skipTests parameter instead.
Default value is: false.
User property is: maven.test.skip.
<skipExec> boolean 2.3 Deprecated. This old parameter is just like skipTests, but bound to the old property maven.test.skip.exec.
User property is: maven.test.skip.exec.
<skipITs> boolean 2.4.3-alpha-2 Set this to 'true' to skip running integration tests, but still compile them. Its use is NOT RECOMMENDED, but quite convenient on occasion.
User property is: skipITs.
<skipTests> boolean 2.4 Set this to 'true' to skip running tests, but still compile them. Its use is NOT RECOMMENDED, but quite convenient on occasion.
User property is: skipTests.
<summaryFiles> File[] 2.6 Additional summary files to read integration test results from.
<testClassesDirectory> File - The directory containing generated test classes of the project being tested. This will be included at the beginning the test classpath.
Default value is: ${project.build.testOutputDirectory}.
<testFailureIgnore> boolean - Set this to true to ignore a failure during testing. Its use is NOT RECOMMENDED, but quite convenient on occasion.
Default value is: false.
User property is: maven.test.failure.ignore.

Parameter Details

<basedir>

The base directory of the project being tested. This can be obtained in your unit test by System.getProperty("basedir").
  • Type: java.io.File
  • Required: No
  • Default: ${basedir}

<encoding>

Deprecated. since of 2.20.1
The character encoding scheme to be applied. Deprecated since 2.20.1 and used encoding UTF-8 in failsafe-summary.xml.
  • Type: java.lang.String
  • Required: No
  • User Property: encoding
  • Default: ${project.reporting.outputEncoding}

<failIfNoTests>

Set this to "true" to cause a failure if there are no tests to run. Defaults to "false".
  • Type: boolean
  • Since: 2.4
  • Required: No
  • User Property: failIfNoTests
  • Default: false

<failOnFlakeCount>

Set this to a value greater than 0 to fail the whole test set if the cumulative number of flakes reaches this threshold. Set to 0 to allow an unlimited number of flakes.
  • Type: int
  • Since: 3.0.0-M6
  • Required: No
  • User Property: failsafe.failOnFlakeCount
  • Default: 0

<packaging>

(no description)
  • Type: java.lang.String
  • Required: No
  • User Property: tycho.verify-test.packaging
  • Default: eclipse-plugin

<reportsDirectory>

Base directory where all reports are written to.
  • Type: java.io.File
  • Required: No
  • Default: ${project.build.directory}/failsafe-reports

<skip>

Set this to 'true' to bypass unit tests entirely. Its use is NOT RECOMMENDED, especially if you enable it using the "maven.test.skip" property, because maven.test.skip disables both running the tests and compiling the tests. Consider using the skipTests parameter instead.
  • Type: boolean
  • Required: No
  • User Property: maven.test.skip
  • Default: false

<skipExec>

Deprecated. Use -DskipTests instead.
This old parameter is just like skipTests, but bound to the old property maven.test.skip.exec.
  • Type: boolean
  • Since: 2.3
  • Required: No
  • User Property: maven.test.skip.exec

<skipITs>

Set this to 'true' to skip running integration tests, but still compile them. Its use is NOT RECOMMENDED, but quite convenient on occasion.
  • Type: boolean
  • Since: 2.4.3-alpha-2
  • Required: No
  • User Property: skipITs

<skipTests>

Set this to 'true' to skip running tests, but still compile them. Its use is NOT RECOMMENDED, but quite convenient on occasion.
  • Type: boolean
  • Since: 2.4
  • Required: No
  • User Property: skipTests

<summaryFile>

The summary file to read integration test results from.
  • Type: java.io.File
  • Required: Yes
  • Default: ${project.build.directory}/failsafe-reports/failsafe-summary.xml

<summaryFiles>

Additional summary files to read integration test results from.
  • Type: java.io.File[]
  • Since: 2.6
  • Required: No

<testClassesDirectory>

The directory containing generated test classes of the project being tested. This will be included at the beginning the test classpath.
  • Type: java.io.File
  • Required: No
  • Default: ${project.build.testOutputDirectory}

<testFailureIgnore>

Set this to true to ignore a failure during testing. Its use is NOT RECOMMENDED, but quite convenient on occasion.
  • Type: boolean
  • Required: No
  • User Property: maven.test.failure.ignore
  • Default: false