Critical Cxx Plugin does not run any tests or produce coverage results, thus test and coverage reports must be created before running the analysis

Unit Test

The C++ plugin supports importing of unit test data from various formats.

Supported Formats

The C++ Plugin parses xunit complaint format using the sonar.cxx.xunit.reportPath. To use other formats, first they need to be converted using the property sonar.cxx.xunit.xsltURL

For convenience the following xsl are provided

• boosttest-1.x-to-junit-1.0.xsl         For transforming Boost-reports
• cpptestunit-1.x-to-junit-1.0.xsl      For transforming CppTestUnit-reports
• cppunit-1.x-to-junit-1.0.xsl            For transforming CppUnit-reports

Coverage

0.2 version supports 3 types of coverage. Unit, Integration and Overall coverage. The following properties should be use to import the coverage reports

• sonar.cxx.coverage.reportPath for unit test coverage
• sonar.cxx.coverage.itReportPath for integration test coverage
• sonar.cxx.coverage.overallReportPath for overall test coverage

Supported Formats

Cobertura and Bullseye (http://www.bullseye.com/) XML formats are supported for > 0.2 versions. Previous versions support only Cobertura, and sonar.cxx.gcovr.reportPath needed to be set.

Gcov / gcovr

• Make sure to compile and link with the --coverage-flag. Disable optimizations and switch on debugging.
• Execute your application / your tests. This will generate .gcda-files.
• Collect the coverage information and generate the report using gcovr:

Bullseye (from 0.2)

• Create xml coverage report 

Merging coverage results to obtain global coverage

• Merging coverage reports for overall coverage
   

Notes about coverage display in sonar:

Sonar <3.2 provides metrics for line coverage and branch coverage. Bullseye users have function and branch/decision coverage instead, the cxx plugin coverts the second directly into branch coverage however line coverage is far more complex and cannot be correlated directly into function coverage.

Line coverage imported from a bullseye report means than function coverage + line branch coverage ( this second occurs since sonar will not display branch coverage if there isn't a line it associated with it). This means also that overall coverage will be affect in sonar and cannot be compared directly to bullseye results. The following pictures illustrate this for a small example project.