Description
The merge command produces coverage data with hits="1" hard-coded for all covered lines.
Steps to reproduce
I have multiple cobertura coverage reports that I want to use dotnet-coverage merge to merge into one.
Consider these coverage files:
TestResults.zip
dotnet-coverage merge TestResults\*xml -r -o merged.cobertura.xml -f cobertura
Expected behavior
I expect the merged report to reflect the hit counts for each line.
In particular, the merged product should report that the {reporoot}\test\Library.Tests\Calculator.cs file's line 17 was hit 3 times.
I get the expected result when merging with the dotnet-reportgenerator-globaltool dotnet CLI tool.
Actual behavior
Every line reported in the merged .xml file reports hits="1".
merged outputs.zip contains outputs from both tools so you can compare.
Description
The
mergecommand produces coverage data withhits="1"hard-coded for all covered lines.Steps to reproduce
I have multiple cobertura coverage reports that I want to use
dotnet-coverage mergeto merge into one.Consider these coverage files:
TestResults.zip
Expected behavior
I expect the merged report to reflect the hit counts for each line.
In particular, the merged product should report that the
{reporoot}\test\Library.Tests\Calculator.csfile's line 17 was hit 3 times.I get the expected result when merging with the
dotnet-reportgenerator-globaltooldotnet CLI tool.Actual behavior
Every line reported in the merged .xml file reports
hits="1".merged outputs.zip contains outputs from both tools so you can compare.