forceZeroCoverage for Unit Test, Integration Test, ...

[guwirth]

We are using the forceZeroCoverage together with Unit Tests. Setting forceZeroCoverage=true will force currently all coverage results to be zero. We do not use Integration Tests at the moment and as a result we see a red line in the source code viewer for Integration Test results. This is very confusing for the users.

Idea is to make this setting adjustable for which coverage it is valid. Should depend in future which key (sonar.cxx.coverage.reportPath, sonar.cxx.coverage.itReportPath, sonar.cxx.coverage.overallReportPath) is defined in the sonar-project.properties file.

Example 1: Force forceZeroCoverage for Unit Tests only (other keys are not defined)

sonar.cxx.coverage.forceZeroCoverage=true
sonar.cxx.coverage.reportPath=reports/coverage-*.xml

Example 2: Force forceZeroCoverage for Unit Tests and Integration Tests

sonar.cxx.coverage.forceZeroCoverage=true
sonar.cxx.coverage.reportPath=reports/coverage-*.xml
sonar.cxx.coverage.itReportPath=