Generic test data
SonarQube Community Build supports generic formats for test coverage and test execution import. If the native output of your coverage tool is not supported by SonarQube Community Build, you must convert it to this format:
Generic test coverage report format
Report paths should be passed in a comma-delimited list to:
sonar.coverageReportPaths
The supported format is described by the sonar-generic-coverage.xsd
:
and looks like this:
The root node should be named coverage
. Its version attribute should be set to 1
.
Insert a file
element for each file which can be covered by tests. Its path
attribute can be either absolute or relative to the root of the module.
Inside a file
element, insert a lineToCover
for each line which can be covered by unit tests. It can have the following attributes:
lineNumber
(mandatory)covered
(mandatory): boolean value indicating whether tests actually hit that linebranchesToCover
(optional): number of branches which can be coveredcoveredBranches
(optional): number of branches which are actually covered by tests
Generic test execution report format
Report paths should be passed in a comma-delimited list to:
The supported format looks like this:
The root node should be named testExecutions
. Its version attribute should be set to 1
.
Insert a file
element for each test file. Its path
attribute can be either absolute or relative to the project's base directory (root module).
Unlike for coverage reports, the files present in the report must be test file names, not source code files covered by tests.
Inside a file
element, insert a testCase
for each test run by unit tests. It can have the following attributes/children:
testCase
(mandatory)name
(mandatory): name of the test caseduration
(mandatory): long value in millisecondsfailure|error|skipped
(optional): if the test is not OK, report its status.
Was this page helpful?