C++ example project for generating test coverage with VisualStudio coverage tool on Azure Pipelines

The test coverage shown here works on both SonarQube and SonarCloud. This project is analysed on SonarCloud!

Note

This simple example aims at demonstrating code coverage in action. It explains how to add coverage on a project for which the analysis is already configured. Some analysis configuration examples are available. Adding code coverage is done the same way regardless of whether you use the Build Wrapper or a Compilation Database to configure the analysis.

To get coverage and feed it to the Sonar Scanner, use the following procedure.

1. In your azure-pipelines.yml file, initialize the extra property sonar.cfamily.vscoveragexml.reportsPath with the path that will contain your XML coverage report

2. Add a VSTest task to launch your tests. Be sure to enable code coverage and to convert the result file into an XML file

3. Make sure the SonarCloudAnalyze task runs after the VSTest task

You can take a look at the sonar-project.properties and azure-pipelines.yml to see it in practice.

Documentation

• Documentation of the C, C++ and Objective-C plugin and its Build Wrapper

• Documentation of using SonarCloud with Azure DevOps

• Configuring C, C++ and Objective-C analysis cache

• Configuring multithreaded execution

• Using compilation database (compile_commands.json)

• Test coverage parameters

Code Description

An example of a flawed C++ code. The code repository can be analyzed automatically, but it can also be compiled with different build systems using different CI pipelines on Linux, macOS, and Windows.

The code repository is forked into other repositories in this collection to add a specific build system, platform, and CI. The downstream repositories are analyzed either with SonarQube or SonarCloud.

You can find examples for:

• Linux

• macOS

• Windows

Using the following build systems:

• CMake

• GNU Autotools

• Xcode

• MSBuild

Running on the following CI services:

• Azure DevOps

• GitHub Actions

• Travis

• Jenkins

• GitLab CI

• BitBucket Pipelines

• Additionally, generic examples demonstrate integration with other CIs and manual-configuration examples should help you if you are running locally.

Configured for analysis on:

• SonarQube

• SonarCloud

You can find also a few examples demonstrating:

• The use of Compilation Database (compile_commands.json)

• Test coverage

See examples-structure.adoc for a description of the structure of this GitHub organization and the relations between its different repositories.