Test execution parameters

This page describes what analysis parameters are needed to import test execution reports into SonarQube.

Test execution reports describe which tests within your test suite have been run during a build.

This differs from test coverage reports, which describe the percentage of your code that has been tested by your test suite during a build. For details, see Overview.

Test execution reports are not generated by SonarQube Server itself. Much like tests coverage reports, test execution reports must be generated by an external tool and then imported into SonarQube Server by specifying a parameter telling the scanner where to look for the report. The data is then displayed in your SonarQube Server analysis.

Below, you will find language- and tool-specific analysis parameters for importing test execution reports.

For information on analysis parameters in general, see Analysis parameters.

Unless otherwise specified, these properties require values that are relative to the project root. Some properties support the following wildcards in paths. The remarks for properties that support wildcards will mention this fact. If wildcards are not noted for a given property, then they are not supported for that property.

Symbol	Meaning
?	a single character
*	any number of characters
**	any number of directories

Branches only

SonarQube Server only supports test execution reports for the branches of a project (including the main branch), not for pull requests. This differs from the case with test coverage reports, where pull requests are supported.

All languages

sonar.testExecutionReportPaths

Comma-delimited list of paths to execution reports in the Generic test data format.

C/C++/Objective-C

sonar.cfamily.cppunit.reportsPath

Path to the directory holding the CPPUnit reports. Note that while measures such as the number of tests are displayed at the project level, no drill-down is available.

C#

sonar.cs.vstest.reportsPaths

Paths to VSTest reports. Multiple paths may be comma-delimited or included via wildcards.

sonar.cs.nunit.reportsPaths

Paths to NUnit execution reports. Multiple paths may be comma-delimited or included via wildcards.

sonar.cs.xunit.reportsPaths

Paths to xUnit execution reports. Multiple paths may be comma-delimited or included via wildcards.

Go

sonar.go.tests.reportPaths

Path to test execution reports generated by Go with -json key, available starting with Go 1.10 (e.g.: go test -json > test-report.out). Paths may be absolute or relative to the project root.

Java

sonar.junit.reportPaths

Comma-delimited list of paths to Surefire XML-format reports.

PHP

sonar.php.tests.reportPath

Path to the PHPUnit unit test execution report file. The path may be absolute or relative to the project root.

Python

sonar.python.xunit.reportPath

Path to unit test execution report. Leave unset to use the default (xunit-reports/xunit-result-*.xml). Path wildcards (see above) are supported. If any paths in the report are invalid, set sonar.python.xunit.skipDetails=true to collect only project-level details.

VB.NET

sonar.vbnet.vstest.reportsPaths

Paths to VSTest execution reports. Multiple paths may be comma-delimited or included via wildcards.

sonar.vbnet.nunit.reportsPaths

Paths to NUnit execution reports. Multiple paths may be comma-delimited or included via wildcards.

sonar.vbnet.xunit.reportsPaths

Paths to xUnit execution reports. Multiple paths may be comma-delimited or included via wildcards.