Currently, the code coverage is measured with the awesome Coverlet library that exports a report in Cobertura format. In the azure-pipelines.yml file, we use the dotnet-reportgenerator-globaltool to create an HTML report and publish those to Azure DevOps.
In Sprint 150 of Azure DevOps native Cobertura support is added to Azure DevOps. We can remove the dotnet-reportgenerator-globaltool from our build pipeline and just publish the cobertura.xml file directly in the PublishCodeCoverageResults step. Azure DevOps will then generate a pretty report.
Blocker: We can only do that when the rollout of Sprint150 of Azure DevOps is completed. Probably May 1, 2019 or later would be good. According to the Azure DevOps changelog the rollout started on April 8, 2019 and would take about 2 to 3 weeks.
Currently, the code coverage is measured with the awesome Coverlet library that exports a report in Cobertura format. In the
azure-pipelines.yml
file, we use the dotnet-reportgenerator-globaltool to create an HTML report and publish those to Azure DevOps.In Sprint 150 of Azure DevOps native Cobertura support is added to Azure DevOps. We can remove the dotnet-reportgenerator-globaltool from our build pipeline and just publish the
cobertura.xml
file directly in the PublishCodeCoverageResults step. Azure DevOps will then generate a pretty report.Blocker: We can only do that when the rollout of Sprint150 of Azure DevOps is completed. Probably May 1, 2019 or later would be good. According to the Azure DevOps changelog the rollout started on April 8, 2019 and would take about 2 to 3 weeks.