Show coverage summary on terminal

[MarcoRossignoli]

Today at the end of the tests msbuil/.net tool drivers show a table with coverage result on console.
For instance:

Calculating coverage result...
  Generating report '/home/vsts/work/1/s/test/coverlet.core.tests/coverage.opencover.xml'

+------------------------------------+--------+--------+--------+
| Module                             | Line   | Branch | Method |
+------------------------------------+--------+--------+--------+
| coverlet.tests.projectsample.empty | 0%     | 100%   | 0%     |
+------------------------------------+--------+--------+--------+
| coverlet.msbuild.tasks             | 0%     | 0%     | 0%     |
+------------------------------------+--------+--------+--------+
| coverlet.core                      | 83.65% | 78.2%  | 84.07% |
+------------------------------------+--------+--------+--------+

+---------+--------+--------+--------+
|         | Line   | Branch | Method |
+---------+--------+--------+--------+
| Total   | 71.74% | 69.83% | 61.9%  |
+---------+--------+--------+--------+
| Average | 27.88% | 59.4%  | 28.02% |
+---------+--------+--------+--------+

This is not supported at the moment for vstest collectors integration.

cc: @vagisha-nidhi @PureKrome

[patricksadowski]

Does VSTest signal the end of the entire test run (like an event)? Each data collector could then do one last action.

[MarcoRossignoli]

No AFAIK...this is the biggest issue for coverlet for a lot of features like merging...we don't have a way to synch between parallel tests run. I'm in contact with vstest team to undestand if there is a solution, but I think that at the moment the only place is inside dotnet cli out of vstest control, btw this is my speculation, we'll see.

[MarcoRossignoli]

For this issue I had a fast conversation with team member and seem that we could inject a custom logger https://github.com/microsoft/vstest-docs/blob/master/docs/report.md

[PureKrome]

Thanks @MarcoRossignoli for working on this issue ASAP. this is the biggest blocker for us, using the vstest collector.

[MarcoRossignoli]

@PureKrome why?Can you tell me how you use terminal data?

[PureKrome]

Sure, either when:

• doing localhost development (to get an idea of the coverage early on)
• CI/CD server (e.g. Azure DevOps or AppVeyor).

using the command line (eg. dotnet test ..) creates a file which I can't read easily. Just seeing the ascii art chart after that command is a great first and easy step into seeing some quick steps.

It's a blocker because it's slowing me down when coding. I don't want to have to push the report file up to codecov.io and then log in to that to review the report.

[MarcoRossignoli]

Ok for local dev you can use ReportGenerator with simple script https://github.com/danielpalme/ReportGenerator