Code Coverage Summary in Build

Required Information

Entering this information will route you directly to the right team and expedite traction.

Question, Bug, or Feature?
Type: Bug

Enter Task Name: Visual Studio Test v2

Environment

• Server - Azure Pipelines https://office.visualstudio.com/Project/_build?definitionId=10497&_a=summary

• Agent - Hosted or Private:

Pool: OE Public Pool
Agent: Agent-APP-ADOBZ-105
Agent name: 'Agent-APP-ADOBZ-105'
Agent machine name: 'APP-ADOBZ-105'
Current agent version: '2.166.2'
Agent running as: 'localAgt'

Issue Description

I have enabled the Code Coverage in the VS Test task

steps:
- task: VSTest@2
  displayName: 'Run unit tests'
  inputs:
    testAssemblyVer2: |
     **\*unittests*.dll
     !**\obj\**
    testFiltercriteria: '(TestCategory!=LocalOnly)&(TestCategory!=IntegrationTests)'
    runSettingsFile: test/TestRunSettings/local.runsettings
    codeCoverageEnabled: true
    platform: '$(BuildPlatform)'
    configuration: '$(BuildConfiguration)'
    publishRunAttachments: false
    diagnosticsEnabled: True

Once the build completes, I could see an option to download the code coverage report on the Code Coverage Tab of the build - But the below section is empty. I was wondering if it is possible to have the code coverage data visualized on the build itself in some tabular format ?

[anshii03]

As of now we will not be able to roll out this new feature.

For better viewing of coverage information you can use -

1.PCC task for coverage information stored in cobertura or jacoco format : https://docs.microsoft.com/en-us/azure/devops/pipelines/tasks/test/publish-code-coverage-results?view=azure-devops

2.Use report generator tool in the pipeline to generate the HTML report (which support good number of coverage formats as input) https://github.com/danielpalme/ReportGenerator

3.Furthermore, to convert .coverage format to .xml fromat : https://github.com/danielpalme/ReportGenerator/wiki/Visual-Studio-Coverage-Tools#vstestconsoleexe

[github-actions[bot]]

This issue is stale because it has been open for 180 days with no activity. Remove the stale label or comment on the issue otherwise this will be closed in 5 days