robotframework:run

Full name:

org.robotframework:robotframework-maven-plugin:2.1.0:run

Description:

Runs the Robot tests. Behaves like invoking the "jybot" command. Robot Framework tests cases are created in files and directories, and they are executed by configuring the path to the file or directory in question to the testCasesDirectory configuration. The given file or directory creates the top-level tests suites, which gets its name, unless overridden with the "name" option, from the file or directory name.

Attributes:

  • Requires a Maven project to be executed.
  • Requires dependency resolution of artifacts in scope: test.
  • Binds by default to the lifecycle phase: integration-test.

Optional Parameters

Name Type Since Description
<argumentFile> File - A text file to read more arguments from.
User property is: argumentFile.
<combinedTagStats> List - Creates combined statistics based on tags. Use the format "tags:title"
<console> String - The overall console output type. It supports the following case-insensitive values. Default is 'verbose'.
  • 'verbose' - Every test suite and test case is reported individually
  • 'dotted' - Only show . for passed test, f for failed non-critical tests, F for failed critical tests, and x for tests which are skipped because test execution exit. Failed critical tests are listed separately after execution. This output type makes it easy to see are there any failures during execution even if there would be a lot of tests.
  • 'quiet' - No output except for errors and warnings.
  • 'none' - No output whatsoever.
Note that CLI shortcuts --dotted and --quiet are not supported.
Default value is: verbose.
<consoleColors> String - Using ANSI colors in console. Normally colors work in unixes but not in Windows. Default is 'on'.
  • 'auto' - Colors are enabled when outputs are written into the console, but not when they are redirected into a file or elsewhere. This is the default.
  • 'on' - Colors are used also when outputs are redirected. Does not work on Windows.
  • 'ansi' - Same as on but uses ANSI colors also on Windows. Useful, for example, when redirecting output to a program that understands ANSI colors.
  • 'off' - Colors are disabled
<consoleWidth> String - Width of the console output. Default is 78.
<criticalTags> List - Tests that have the given tags are considered critical.
<debugFile> File - A debug file that is written during execution.
<document> String - Sets the documentation of the top-level tests suites.
<dryrun> boolean - Sets dryrun mode on use. In the dry run mode tests are run without executing keywords originating from test libraries. Useful for validating test data syntax.
Default value is: false.
<excludes> List - Selects the tests cases by tags.
<excludes_cli> String - Selects the tests cases by tags. Given as a comma separated list. This setting overrides the value for excludes configuration in pom.xml.

Example:

mvn -Dexcludes=foo,bar verify
(This setting is needed to support overriding the configuration value from command prompt on maven 2.)


User property is: excludes.
<exitOnFailure> boolean - Sets robot to stop execution immediately if a critical test fails.
Default value is: false.
<externalRunner> ExternalRunnerConfiguration -

Test are executed in a new process if this configuration is used.

The classpath for the new process will include by default all the test scope dependencies from the pom.

  • Environment variables can be added with environmentVariables map. CLASSPATH environment variable is added (prepended) to the default dependencies.
  • excludeDependencies can be used to exclude the test scope dependencies from the classpath of the new process.
  • jvmArgs can be used to specify JVM options
  • runnerClass can be used to specify runner class
  • runWithPython can be used to specify running with Python Robot Framework
Example: 

<externalRunner>
     <environmentVariables>
         <foo>bar</foo>
         <CLASSPATH>this-should-be-seen-by-external-process.jar</CLASSPATH>
     </environmentVariables>
     <jvmArgs>
         <jvmArg>-XX:PermSize=128m</jvmArg>
         <jvmArg>-XX:MaxPermSize=256m</jvmArg>
         <jvmArg>-Xmx512m</jvmArg>
     </jvmArgs>
     <excludeDependencies>true</excludeDependencies>
     <runnerClass>org.robotframework.RobotFramework</runnerClass>
     <runWithPython>false</runWithPython>
</externalRunner>

<extraPathDirectories> File[] - Additional locations (directories, ZIPs, JARs) where to search test libraries from when they are imported. Maps to Jybot's --pythonpath option. Otherwise if no locations are declared, the default location is ${project.basedir}/src/test/resources/robotframework/libraries.
<flattenKeywords> List - Flatten keywords and their messages altogether. Instructions at http://robotframework.org/robotframework/latest/RobotFrameworkUserGuide.html#flattening-keywords.
  • 'FOR' - Flatten for loops fully.
  • 'FORITEM' - Flatten individual for loop iterations.
  • 'NAME:<pattern>' - Flatten keywords matching the given pattern.
  • 'TAG:<pattern>' - Flatten keywords with tags matching the given pattern.
The <pattern> is case, space, and underscore insensitive, and it supports simple patterns with * and ? as wildcards.
<includes> List - Selects the tests cases by tags.
<includes_cli> String - Selects the tests cases by tags. Given as a comma separated list. This setting overrides the value for includes configuration in pom.xml.

Example:

mvn -Dincludes=foo,bar verify
(This setting is needed to support overriding the configuration value from command prompt on maven 2.)


User property is: includes.
<listener> String - Sets a single listener for monitoring tests execution, can also be set via commandline using -Dlistener=MyListener.
User property is: listener.
<listeners> List - Sets multiple listeners for monitoring tests execution. Use the format "ListenerWithArgs:arg1:arg2" or simply "ListenerWithoutArgs"
<log> File - Sets the path to the generated log file.
<logLevel> String - Sets the threshold level for logging.
<logTitle> String - Sets a title for the generated tests log.
<metadata> List - Sets free metadata for the top level tests suites.
<name> String - Sets the name of the top-level tests suites.
<noStatusReturnCode> boolean - If true, sets the return code to zero regardless of failures in test cases. Error codes are returned normally.
Default value is: false.
<nonCriticalTags> List - Tests that have the given tags are not critical.
<output> File - Sets the path to the generated output file.
<outputDirectory> File - Configures where generated reports are to be placed.
Default value is: ${project.build.directory}/robotframework-reports.
<randomize> String - Sets the test execution order to be randomized. Valid values are all, suite, and test
<removeKeywords> List - Remove keywords and their messages altogether. Instructions at http://robotframework.org/robotframework/latest/RobotFrameworkUserGuide.html#removing-keywords.
  • 'ALL' - Remove data from all keywords unconditionally.
  • 'PASSED' -Remove keyword data from passed test cases. In most cases, log files created using this option contain enough information to investigate possible failures.
  • 'FOR' - Remove all passed iterations from for loops except the last one.
  • 'WUKS' - Remove all failing keywords inside BuiltIn keyword 'Wait Until Keyword Succeeds' except the last one.
  • 'NAME:<pattern>' - Remove data from all keywords matching the given pattern regardless the keyword status.
  • 'TAG:<pattern>' - Remove data from keywords with tags that match the given pattern.
The <pattern> is case, space, and underscore insensitive, and it supports simple patterns with * and ? as wildcards.
<report> File - Sets the path to the generated report file.
<reportBackground> String - Sets background colors for the generated report and summary.
<reportTitle> String - Sets a title for the generated tests report.
<rerunFailed> boolean - Run only failed test cases. Note that output.xml has to be available. By default clean goal would remove output.xml making it impossible to run failed cases.
User property is: rerunfailed.
<rpa> boolean - Turn on generic automation mode.
Default value is: false.
<runEmptySuite> boolean - Executes tests also if the top level test suite is empty. Useful e.g. with --include/--exclude when it is not an error that no test matches the condition.
Default value is: false.
<runMode> String - Sets the execution mode for this tests run. Note that this setting has been deprecated in Robot Framework 2.8. Use separate dryryn, skipTeardownOnExit, exitOnFailure, and randomize settings instead.
<skip> boolean - Skip tests, bound to -Dmaven.test.skip, which suppresses test compilation as well.
Default value is: false.
User property is: maven.test.skip.
<skipATs> boolean - Skip acceptance tests executed by this plugin. Bound to -DskipATs. This allows to run tests and integration tests, but no acceptance tests.
User property is: skipATs.
<skipITs> boolean - Skip acceptance tests executed by this plugin together with other integration tests, e.g. tests run by the maven-failsafe-plugin. Bound to -DskipITs
User property is: skipITs.
<skipTeardownOnExit> boolean - Sets whether the teardowns are skipped if the test execution is prematurely stopped.
Default value is: false.
<skipTests> boolean - Skip tests. Bound to -DskipTests. This allows to skip acceptance tests together with all other tests.
User property is: skipTests.
<skiponfailures> List - Tests having given tag will be skipped if they fail. Tag can be a pattern. New in RF 4.0.
<skiponfailures_cli> String - Report test cases as skipped instead of failed by tags. Given as a comma separated list. This setting overrides the value for skiponfailures configuration in pom.xml.

Example:

mvn -Dskiponfailure=foo,bar verify
(This setting is needed to support overriding the configuration value from command prompt on maven 2.)


User property is: skiponfailures.
<skips> List - Tests having given tag will be skipped. Tag can be a pattern. New in RF 4.0.
<skips_cli> String - Skip the tests cases by tags. Given as a comma separated list. This setting overrides the value for skips configuration in pom.xml.

Example:

mvn -Dskips=foo,bar verify
(This setting is needed to support overriding the configuration value from command prompt on maven 2.)


User property is: skips.
<splitOutputs> String - Splits output and log files.
<suiteStatLevel> String - Defines how many levels to show in the Statistics by Suite table in outputs.
<suites> List - Selects the tests suites by name.
<suites_cli> String - Selects the tests suites by name. Given as a comma separated list. This setting overrides the value for suites configuration in pom.xml.

Example:

mvn -Dsuites=foo,bar verify
(This setting is needed to support overriding the configuration value from command prompt on maven 2.)


User property is: suites.
<summaryTitle> String - Sets a title for the generated summary report.
<tagDocs> List - Adds documentation to the specified tags.
<tagStatExcludes> List - Excludes these tags from the Statistics by Tag and Test Details by Tag tables in outputs.
<tagStatIncludes> List - Includes only these tags in the Statistics by Tag and Test Details by Tag tables in outputs.
<tagStatLinks> List - Adds external links to the Statistics by Tag table in outputs. Use the format "pattern:link:title"
<tags> List - Sets the tags(s) to all executed tests cases.
<tasks> List - Selects the tasks cases by name.
<tasks_cli> String - Selects the tasks by name. Given as a comma separated list. This setting overrides the value for tasks configuration in pom.xml.

Example:

mvn -Dtasks=foo,bar verify
(This setting is needed to support overriding the configuration value from command prompt on maven 2.)


User property is: tasks.
<testCasesDirectory> File - The directory where the test cases are located.
Default value is: ${project.basedir}/src/test/robotframework/acceptance.
User property is: testCasesDirectory.
<tests> List - Selects the tests cases by name.
<tests_cli> String - Selects the tests cases by name. Given as a comma separated list. This setting overrides the value for tests configuration in pom.xml.

Example:

mvn -Dtests=foo,bar verify
(This setting is needed to support overriding the configuration value from command prompt on maven 2.)


User property is: tests.
<timestampOutputs> boolean - Adds a timestamp to all output files.
<variableFiles> List - Sets variables using variables files. Use the format "path:args"
<variables> List - Sets individual variables. Use the format "name:value"
<variables_cli> String - Sets individual variables. Use the format "name:value" and separate entries with comma. These are added into variables defined in the pom (variables with same name are overridden). (This setting is needed to support overriding the configuration value from command prompt on maven 2.)
User property is: variables.
<warnOnSkippedFiles> boolean - Show a warning when an invalid file is skipped.
<xunitFile> File - Sets the path to the generated XUnit compatible result file, relative to outputDirectory. The file is in xml format. By default, the file name is derived from the testCasesDirectory parameter, replacing blanks in the directory name by underscores.

Parameter Details

<argumentFile>

A text file to read more arguments from.
  • Type: java.io.File
  • Required: No
  • User Property: argumentFile

<combinedTagStats>

Creates combined statistics based on tags. Use the format "tags:title"
  • Type: java.util.List
  • Required: No

<console>

The overall console output type. It supports the following case-insensitive values. Default is 'verbose'.
  • 'verbose' - Every test suite and test case is reported individually
  • 'dotted' - Only show . for passed test, f for failed non-critical tests, F for failed critical tests, and x for tests which are skipped because test execution exit. Failed critical tests are listed separately after execution. This output type makes it easy to see are there any failures during execution even if there would be a lot of tests.
  • 'quiet' - No output except for errors and warnings.
  • 'none' - No output whatsoever.
Note that CLI shortcuts --dotted and --quiet are not supported.
  • Type: java.lang.String
  • Required: No
  • Default: verbose

<consoleColors>

Using ANSI colors in console. Normally colors work in unixes but not in Windows. Default is 'on'.
  • 'auto' - Colors are enabled when outputs are written into the console, but not when they are redirected into a file or elsewhere. This is the default.
  • 'on' - Colors are used also when outputs are redirected. Does not work on Windows.
  • 'ansi' - Same as on but uses ANSI colors also on Windows. Useful, for example, when redirecting output to a program that understands ANSI colors.
  • 'off' - Colors are disabled
  • Type: java.lang.String
  • Required: No

<consoleWidth>

Width of the console output. Default is 78.
  • Type: java.lang.String
  • Required: No

<criticalTags>

Tests that have the given tags are considered critical.
  • Type: java.util.List
  • Required: No

<debugFile>

A debug file that is written during execution.
  • Type: java.io.File
  • Required: No

<document>

Sets the documentation of the top-level tests suites.
  • Type: java.lang.String
  • Required: No

<dryrun>

Sets dryrun mode on use. In the dry run mode tests are run without executing keywords originating from test libraries. Useful for validating test data syntax.
  • Type: boolean
  • Required: No
  • Default: false

<excludes>

Selects the tests cases by tags.
  • Type: java.util.List
  • Required: No

<excludes_cli>

Selects the tests cases by tags. Given as a comma separated list. This setting overrides the value for excludes configuration in pom.xml.

Example:

mvn -Dexcludes=foo,bar verify
(This setting is needed to support overriding the configuration value from command prompt on maven 2.)

  • Type: java.lang.String
  • Required: No
  • User Property: excludes

<exitOnFailure>

Sets robot to stop execution immediately if a critical test fails.
  • Type: boolean
  • Required: No
  • Default: false

<externalRunner>

Test are executed in a new process if this configuration is used.

The classpath for the new process will include by default all the test scope dependencies from the pom.

  • Environment variables can be added with environmentVariables map. CLASSPATH environment variable is added (prepended) to the default dependencies.
  • excludeDependencies can be used to exclude the test scope dependencies from the classpath of the new process.
  • jvmArgs can be used to specify JVM options
  • runnerClass can be used to specify runner class
  • runWithPython can be used to specify running with Python Robot Framework
Example: 

<externalRunner>
     <environmentVariables>
         <foo>bar</foo>
         <CLASSPATH>this-should-be-seen-by-external-process.jar</CLASSPATH>
     </environmentVariables>
     <jvmArgs>
         <jvmArg>-XX:PermSize=128m</jvmArg>
         <jvmArg>-XX:MaxPermSize=256m</jvmArg>
         <jvmArg>-Xmx512m</jvmArg>
     </jvmArgs>
     <excludeDependencies>true</excludeDependencies>
     <runnerClass>org.robotframework.RobotFramework</runnerClass>
     <runWithPython>false</runWithPython>
</externalRunner>
  • Type: org.robotframework.mavenplugin.ExternalRunnerConfiguration
  • Required: No

<extraPathDirectories>

Additional locations (directories, ZIPs, JARs) where to search test libraries from when they are imported. Maps to Jybot's --pythonpath option. Otherwise if no locations are declared, the default location is ${project.basedir}/src/test/resources/robotframework/libraries.
  • Type: java.io.File[]
  • Required: No

<flattenKeywords>

Flatten keywords and their messages altogether. Instructions at http://robotframework.org/robotframework/latest/RobotFrameworkUserGuide.html#flattening-keywords.
  • 'FOR' - Flatten for loops fully.
  • 'FORITEM' - Flatten individual for loop iterations.
  • 'NAME:<pattern>' - Flatten keywords matching the given pattern.
  • 'TAG:<pattern>' - Flatten keywords with tags matching the given pattern.
The <pattern> is case, space, and underscore insensitive, and it supports simple patterns with * and ? as wildcards.
  • Type: java.util.List
  • Required: No

<includes>

Selects the tests cases by tags.
  • Type: java.util.List
  • Required: No

<includes_cli>

Selects the tests cases by tags. Given as a comma separated list. This setting overrides the value for includes configuration in pom.xml.

Example:

mvn -Dincludes=foo,bar verify
(This setting is needed to support overriding the configuration value from command prompt on maven 2.)

  • Type: java.lang.String
  • Required: No
  • User Property: includes

<listener>

Sets a single listener for monitoring tests execution, can also be set via commandline using -Dlistener=MyListener.
  • Type: java.lang.String
  • Required: No
  • User Property: listener

<listeners>

Sets multiple listeners for monitoring tests execution. Use the format "ListenerWithArgs:arg1:arg2" or simply "ListenerWithoutArgs"
  • Type: java.util.List
  • Required: No

<log>

Sets the path to the generated log file.
  • Type: java.io.File
  • Required: No

<logLevel>

Sets the threshold level for logging.
  • Type: java.lang.String
  • Required: No

<logTitle>

Sets a title for the generated tests log.
  • Type: java.lang.String
  • Required: No

<metadata>

Sets free metadata for the top level tests suites.
  • Type: java.util.List
  • Required: No

<name>

Sets the name of the top-level tests suites.
  • Type: java.lang.String
  • Required: No

<noStatusReturnCode>

If true, sets the return code to zero regardless of failures in test cases. Error codes are returned normally.
  • Type: boolean
  • Required: No
  • Default: false

<nonCriticalTags>

Tests that have the given tags are not critical.
  • Type: java.util.List
  • Required: No

<output>

Sets the path to the generated output file.
  • Type: java.io.File
  • Required: No

<outputDirectory>

Configures where generated reports are to be placed.
  • Type: java.io.File
  • Required: No
  • Default: ${project.build.directory}/robotframework-reports

<randomize>

Sets the test execution order to be randomized. Valid values are all, suite, and test
  • Type: java.lang.String
  • Required: No

<removeKeywords>

Remove keywords and their messages altogether. Instructions at http://robotframework.org/robotframework/latest/RobotFrameworkUserGuide.html#removing-keywords.
  • 'ALL' - Remove data from all keywords unconditionally.
  • 'PASSED' -Remove keyword data from passed test cases. In most cases, log files created using this option contain enough information to investigate possible failures.
  • 'FOR' - Remove all passed iterations from for loops except the last one.
  • 'WUKS' - Remove all failing keywords inside BuiltIn keyword 'Wait Until Keyword Succeeds' except the last one.
  • 'NAME:<pattern>' - Remove data from all keywords matching the given pattern regardless the keyword status.
  • 'TAG:<pattern>' - Remove data from keywords with tags that match the given pattern.
The <pattern> is case, space, and underscore insensitive, and it supports simple patterns with * and ? as wildcards.
  • Type: java.util.List
  • Required: No

<report>

Sets the path to the generated report file.
  • Type: java.io.File
  • Required: No

<reportBackground>

Sets background colors for the generated report and summary.
  • Type: java.lang.String
  • Required: No

<reportTitle>

Sets a title for the generated tests report.
  • Type: java.lang.String
  • Required: No

<rerunFailed>

Run only failed test cases. Note that output.xml has to be available. By default clean goal would remove output.xml making it impossible to run failed cases.
  • Type: boolean
  • Required: No
  • User Property: rerunfailed

<rpa>

Turn on generic automation mode.
  • Type: boolean
  • Required: No
  • Default: false

<runEmptySuite>

Executes tests also if the top level test suite is empty. Useful e.g. with --include/--exclude when it is not an error that no test matches the condition.
  • Type: boolean
  • Required: No
  • Default: false

<runMode>

Sets the execution mode for this tests run. Note that this setting has been deprecated in Robot Framework 2.8. Use separate dryryn, skipTeardownOnExit, exitOnFailure, and randomize settings instead.
  • Type: java.lang.String
  • Required: No

<skip>

Skip tests, bound to -Dmaven.test.skip, which suppresses test compilation as well.
  • Type: boolean
  • Required: No
  • User Property: maven.test.skip
  • Default: false

<skipATs>

Skip acceptance tests executed by this plugin. Bound to -DskipATs. This allows to run tests and integration tests, but no acceptance tests.
  • Type: boolean
  • Required: No
  • User Property: skipATs

<skipITs>

Skip acceptance tests executed by this plugin together with other integration tests, e.g. tests run by the maven-failsafe-plugin. Bound to -DskipITs
  • Type: boolean
  • Required: No
  • User Property: skipITs

<skipTeardownOnExit>

Sets whether the teardowns are skipped if the test execution is prematurely stopped.
  • Type: boolean
  • Required: No
  • Default: false

<skipTests>

Skip tests. Bound to -DskipTests. This allows to skip acceptance tests together with all other tests.
  • Type: boolean
  • Required: No
  • User Property: skipTests

<skiponfailures>

Tests having given tag will be skipped if they fail. Tag can be a pattern. New in RF 4.0.
  • Type: java.util.List
  • Required: No

<skiponfailures_cli>

Report test cases as skipped instead of failed by tags. Given as a comma separated list. This setting overrides the value for skiponfailures configuration in pom.xml.

Example:

mvn -Dskiponfailure=foo,bar verify
(This setting is needed to support overriding the configuration value from command prompt on maven 2.)

  • Type: java.lang.String
  • Required: No
  • User Property: skiponfailures

<skips>

Tests having given tag will be skipped. Tag can be a pattern. New in RF 4.0.
  • Type: java.util.List
  • Required: No

<skips_cli>

Skip the tests cases by tags. Given as a comma separated list. This setting overrides the value for skips configuration in pom.xml.

Example:

mvn -Dskips=foo,bar verify
(This setting is needed to support overriding the configuration value from command prompt on maven 2.)

  • Type: java.lang.String
  • Required: No
  • User Property: skips

<splitOutputs>

Splits output and log files.
  • Type: java.lang.String
  • Required: No

<suiteStatLevel>

Defines how many levels to show in the Statistics by Suite table in outputs.
  • Type: java.lang.String
  • Required: No

<suites>

Selects the tests suites by name.
  • Type: java.util.List
  • Required: No

<suites_cli>

Selects the tests suites by name. Given as a comma separated list. This setting overrides the value for suites configuration in pom.xml.

Example:

mvn -Dsuites=foo,bar verify
(This setting is needed to support overriding the configuration value from command prompt on maven 2.)

  • Type: java.lang.String
  • Required: No
  • User Property: suites

<summaryTitle>

Sets a title for the generated summary report.
  • Type: java.lang.String
  • Required: No

<tagDocs>

Adds documentation to the specified tags.
  • Type: java.util.List
  • Required: No

<tagStatExcludes>

Excludes these tags from the Statistics by Tag and Test Details by Tag tables in outputs.
  • Type: java.util.List
  • Required: No

<tagStatIncludes>

Includes only these tags in the Statistics by Tag and Test Details by Tag tables in outputs.
  • Type: java.util.List
  • Required: No

<tagStatLinks>

Adds external links to the Statistics by Tag table in outputs. Use the format "pattern:link:title"
  • Type: java.util.List
  • Required: No

<tags>

Sets the tags(s) to all executed tests cases.
  • Type: java.util.List
  • Required: No

<tasks>

Selects the tasks cases by name.
  • Type: java.util.List
  • Required: No

<tasks_cli>

Selects the tasks by name. Given as a comma separated list. This setting overrides the value for tasks configuration in pom.xml.

Example:

mvn -Dtasks=foo,bar verify
(This setting is needed to support overriding the configuration value from command prompt on maven 2.)

  • Type: java.lang.String
  • Required: No
  • User Property: tasks

<testCasesDirectory>

The directory where the test cases are located.
  • Type: java.io.File
  • Required: No
  • User Property: testCasesDirectory
  • Default: ${project.basedir}/src/test/robotframework/acceptance

<tests>

Selects the tests cases by name.
  • Type: java.util.List
  • Required: No

<tests_cli>

Selects the tests cases by name. Given as a comma separated list. This setting overrides the value for tests configuration in pom.xml.

Example:

mvn -Dtests=foo,bar verify
(This setting is needed to support overriding the configuration value from command prompt on maven 2.)

  • Type: java.lang.String
  • Required: No
  • User Property: tests

<timestampOutputs>

Adds a timestamp to all output files.
  • Type: boolean
  • Required: No

<variableFiles>

Sets variables using variables files. Use the format "path:args"
  • Type: java.util.List
  • Required: No

<variables>

Sets individual variables. Use the format "name:value"
  • Type: java.util.List
  • Required: No

<variables_cli>

Sets individual variables. Use the format "name:value" and separate entries with comma. These are added into variables defined in the pom (variables with same name are overridden). (This setting is needed to support overriding the configuration value from command prompt on maven 2.)
  • Type: java.lang.String
  • Required: No
  • User Property: variables

<warnOnSkippedFiles>

Show a warning when an invalid file is skipped.
  • Type: boolean
  • Required: No

<xunitFile>

Sets the path to the generated XUnit compatible result file, relative to outputDirectory. The file is in xml format. By default, the file name is derived from the testCasesDirectory parameter, replacing blanks in the directory name by underscores.
  • Type: java.io.File
  • Required: No