How to display a detailed code coverage report by default #19295
Labels
Comments
|
For reference: Basic coverage report |
|
For reference: Detailed Report |
|
For reference: |
|
For reference: PublishCodeCoverageResults task log |
|
Possibly related to #19221 |
We are also seeing this behaviour. The strange thing is, that while the pipeline is still running, the A StackOverflow page with the same observation presents the fixing of a wrong |
|
+1 |
|
Same issue here. I had to rollback to V1 task to make the detail report visible again. And, even so, it took me a while to figure out I had to add |
|
Based on the reactions of the senior program manager in the post New version of Publish Code Coverage Results task: View actual source code:
Usage of ReportGenerator:
Branch based code coverage:
Gap between v1 and v2:
|
|
I don't understand why this huge gap in functionality going from V1 to V2 isn't documented anywhere? Especially on the official documentation page. |
|
I was using reportgenerator@5 with PublishCodeCoverageResults@1 Now I have migrated to PublishCodeCoverageResults@2 without using report generator based the previous conversation in github because PublishCodeCoverageResults@2 doesn't support report generator. Post migration I don't see any results. please find reference below
|
|
Check this link: danielpalme/ReportGenerator#646 (comment) |
|
Hi @rikrak, did you get any solution for this? |
|
@DevTestUser123 No I didn't, but this might be of interest: I haven't had chance to try it yet, but it looks promising |
Yep that helps, thank you for this. But I am rooting for a solution with PublishCodeCoverageV2 only, it's very weird to me that it is storing detailed report in Artifact but why it is generating very basic report in code coverage pipeline tab. |
|
From my experience (and anecdotally, the experience of others) the |
|
##[warning]New V2 version of task publishing code coverage results is available to all our customers now. We highly recommend to stop using the V1 version and migrate to V2 version This is the only reason I want to migrate to V2 because, in the future, all updates are going to be part of V2. |
|
How come we are getting warnings to use V2 but V2 still does not match the functionality of the V1 detailed report? As long as this basic functionality is missing there should not be a warning imho. Showing a warning will just make ppl try out V2 only to find out they have to go back to V1 again wasting our time. |
I've quickly read the source code and it seems that this task still use ReportGenerator under the hood because it use 'azure-pipelines-coveragegenerator' that rely on ReportGenerator: git link. So the Senior Program Manager doesn't give us a good explaination. |
|
I don't know why there is no info about the detailed and summary version. I would expect that the new version includes better reporting not worse |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Task name
PublishCodeCoverageResults
Task version
2
Environment type (Please select at least one enviroment where you face this issue)
Azure DevOps Server type
dev.azure.com (formerly visualstudio.com)
Azure DevOps Server Version (if applicable)
No response
Operation system
Windows 10
Question
I have a pipeline that builds a .NET Framework project and runs MSTests, collecting code coverage using the NuGet package coverlet.collector (V6.0.0). The coverage results are published using the PublishCodeCoverageResults@2 task[1]
The coverage results are published to the pipeline successfully, which is great.
When I look at the Code Coverage tab on the build summary, I see a very basic report. There is, however, a more detailed report uploaded as a build artifact called "Code Coverage Report_< BuildId >" which is far more useful. Is there any way of having this displayed as the default coverage report?
Note: Could be related to #19221
[1]
- task: DotNetCoreCLI@2 displayName: 'Run Unit Tests' inputs: command: test projects: | **\Tests.Unit.*.csproj publishTestResults: false arguments: -c $(buildConfiguration) --logger trx --no-build --settings .\DevopsTestRun.runsettings - task: PublishTestResults@2 displayName: 'Publish Test Results' condition: succeededOrFailed() inputs: testResultsFormat: VSTest testResultsFiles: '$(Build.SourcesDirectory)\TestResults\**\*.trx' failTaskOnMissingResultsFile: true - task: PublishCodeCoverageResults@2 displayName: 'Publish code coverage' condition: succeededOrFailed() inputs: summaryFileLocation: | $(Build.SourcesDirectory)/TestResults/**/coverage.cobertura.xml !**/In/**/coverage.cobertura.xml pathToSources: '$(Build.SourcesDirectory)'The text was updated successfully, but these errors were encountered: