Azure-pipelines-tasks: Code coverage results is empty (except for download link)

[TekuSP]

Code coverage tab is empty. Expected behaviour like in #9954 (https://github.com/microsoft/azure-pipelines-tasks/issues/9954#issuecomment-572450388)

Please fix it, or add our organization to closed beta. This is critical feature for us.

[zingaroo]

Any update on when this will be released?

[ankit-arora12]

@TekuSP @zingaroo
Thank you for expressing interest in trying the new feature.
Due to some unforeseen circumstances, we are unable to enroll new customers for the private preview at this time.
Right now, we don’t have an ETA to share on when we can roll this out more broadly for customers to try. Sorry !

[anshii03]

@TekuSP @zingaroo
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

[ShreyasRmsft]

Closing this based on the comment above.

[TekuSP]

Bug is not resolved, close this bug when you finish your code coverage tab.
Until then, let it be red, bad number in your dashboard.

Devops is paid service, and we pay not small amount of money for it. Fix your bugs.

[TekuSP]

@anshii03 @ShreyasRmsft @ankit-arora12 Reopen the issue, or give me migration path to other service, like TeamCity and Jira, for our whole organization.
This is everything wrong

1. It's open from spring, promising feature
2. Feature is not there, but tab is
3. Marking bug as a question
4. Closing this issue, so you have clean agile plan
5. Almost no communication

Reopen the issue, and close it when you fixed it, not sooner.
If you have problem with that, give me email to your manager, and I will gladly write them long email explaining the situation. I am sure they would be happy to hear about no communication and half year long reported bug, closed.

[shashban]

@TekuSP
We had tried a closed preview of the capability to view code coverage details for a build. Based on the feedback and monitoring of the limited usage, we have now taken it back.
The behavior you are observing above is not a bug, it is the by design behavior as of now. @anshii03 shared the available alternatives earlier on this thread.

We don't have a timeline to share for when we may be working on this issue again.

Thanks

[TekuSP]

Okay, then why TAB IS STILL THERE?

If this is a feature which is not implemented, remove the whole TAB.
@shashban