Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 37 Next »

Table of Contents

Requirements

  • Unit / integration tests must be isolated from the main code base in dedicated VisuitProjectPatternal Studio projects.
  • Test framework(s) must be compatible with Gallio.

Unit Tests and Code Coverage

There are two different ways to feed the SonarQube platform with information on unit tests execution and code coverage:

  1. Let the SonarQube platform drive the execution of the unit tests and the code coverage tool
  2. Reuse reports that have been generated by external tools prior to the SonarQube analysis

These two ways are handled by Gallio. So you first have to install Gallio on the machine(s) running the SonarQube analysis. You also have to install the code coverage tool of your choice that will be driven by Gallio. Supported tools are dotCover, NCover, OpenCover and PartCover.

Configuring Gallio

Log in as a System administrator and go to Settings > Configuration > General Settings > .NET Gallio.

  • Set the path to the Gallio installation directory through the sonar.gallio.installDirectory property.
  • Define which tool to use to compute the code coverage through the sonar.gallio.coverage.tool property. Then, set the installation directory of this code coverage tool through the sonar.dotcover.installDirectory or sonar.opencover.installDirectory or sonar.partcover.installDirectory property. Note that there is not such a property for NCover as the installation path of NCover is automatically discovered by Gallio.

Letting the SonarQube platform drive the execution of the unit tests and the code coverage tool

This is the default mode.

The first and unique step is to tell SonarQube which projects are unit test projects. To do so, set the sonar.dotnet.visualstudio.testProjectPattern property.

Then, you just have to run a SonarQube analysis and you'll get data on unit tests and code coverage. Indeed, the paths to the unit test assemblies are automatically retrieved from the Visual Studio ".csproj" files. And the execution of unit tests and the driving of the coverage tool is automatically performed by Gallio.

Reusing existing reports

To activate this mode, add the following line to your project configuration file:

Then, you just need to provide SonarQube with the following reports: unit tests execution and code coverage.

The following command lines are launched while letting the SonarQube platform drive the execution of the unit tests and the code coverage tool. The reuseReport mode has been tested with those command lines. That's why it is highly recommend to generate your reports using similar command lines:

Deactivating Unit Tests and Code Coverage

Add the following line to your analysis configuration file:

Integration Tests and Code Coverage

Because the principles are very similar to those for unit tests, please read Unit Tests and Code Coverage.

Letting the SonarQube platform drive the execution of the unit tests and the code coverage tool

To activate this mode, add the following line to your analysis configuration file:

The first and unique step is to tell SonarQube which projects are integration test projects. To do so, set the sonar.dotnet.visualstudio.itProjectPattern property.

Then, you just have to run a SonarQube analysis and you'll get data on integration tests and code coverage. Indeed, the paths to the integration test assemblies are automatically retrieved from the Visual Studio ".csproj" files. And the execution of integration tests and the driving of the coverage tool is automatically performed by Gallio.

Reusing existing reports

To activate this mode, add the following line to your project configuration file:

Then, you just need to provide SonarQube with the following reports: integration tests execution report and code coverage report.

Due to SONAR-4101, execution data for integration tests are not currently stored as such. Thus, the C# plugin merges integration test data with unit test data.

Deactivating Integration Tests and Code Coverage

This is the default mode.

FAQ

My unit tests and integration tests are defined within the same project, how can I run my unit tests only?

Define the sonar.gallio.filter property (or the sonar.gallio.it.filter property for integration tests):

Note that Gallio does not support MSTest categories. Thus it is useless to specify this property when MSTest is used.

How can I exclude some specific projects and/or namespaces from code coverage computation?

Define the sonar.gallio.coverage.excludes property. Note that this property is shared between unit and integration tests.

SonarQube cannot retrieve the unit test assemblies

See Running an Analysis on a C# Solution, "SonarQube cannot retrieve the assemblies" section.

0% code coverage in reuseReport mode

This might happen if you have generated the reports then moved the files of your solution. Indeed, in the XML coverage files, the paths to the C# source files must be the same as the paths specified in the ".csproj" files, otherwise the coverage data are simply not taken into account.

When using OpenCover with Gallio, I get 0% code coverage, but I do have test classes that are covered by tests

Most probably, you should use the following property to run the tests in an isolated process:

As describe in the Gallio documentation, possible values are IsolatedAppDomain (PartCover default runner type), IsolatedProcess and Local. Does not apply to NCover.

Gallio execution fails with following error message

This error happens when one of the dotnet config files (app.config, web.config, ...) of your Visual Studio solution specifies a runtime version not supported by the instance of Gallio. This is often the case when the following XML fragment appears in an app.config file:

The "sku" attribute is not something understandable by Gallio. If you replace the above XML fragment with the one below, the issue is solved:

NCover, the analysis succeeded but only one test project is taken into account

The NCover Complete Edition allows you to run tests from multiple projects and merge the coverage data, the NCover Classic Edition does not.

The workaround is to activate the Gallio safe mode (sonar.gallio.safe.mode=true). Gallio will then be launched for each test project and the generated XML reports will be merged.

How to set Gallio's timeout?

Set the sonar.gallio.timeoutMinutes property (default value is 30).

How can I run Gallio and PartCover on 64-bit Windows?

Gallio and PartCover work perfectly out-of-the-box on x86 Windows, but not on 64-bit versions. To make them work:

  1. Download the latest Gallio x64 installer and install it in a folder, but not under "Program Files".
  2. Download the latest PartCover installer and install it in a folder, but not under "Program Files".
  3. Run corflags.exe on Gallio and PartCover executables:

See http://www.planetgeek.ch/2009/10/15/get-partcover-running-on-x64-windows/

Gallio execution fails on a Windows 64-bit system

If in the logs you get something such as:

it might be because some of your assemblies have been compiled with a x86 profile (32 bits) while Gallio is configured to run in an "Any CPU" mode, hence 64bits on your system.
This problem might be solved using corflags tool to force Gallio to run in a 32 bits mode as shown below:

Some tests fail unexpectedly using a legacy .net2 library

If you get this kind of error:

It is likely that you are facing the issue described here

The problem might be solved if you modify your installation of Gallio. Add the following XML fragment in files Gallio.Host.x86.exe.config and/or Gallio.Host.x64.exe.config:

  • No labels