Display code coverage report on console on dotnet test --collect "Code Coverage"

[smadala]

Description

• dotnet test --collect "Code coverage" should show coverage info for each module on console

Steps to reproduce

• dotnet new mstest
• dotnet add package spekt.vstest.coverage.report --version 0.0.1-beta-01 --source https://www.myget.org/F/spekt/api/v3/index.json
• dotnet test --collect "Code coverage"

Expected behavior

Something similar to below image

Actual behavior

• dotnet test just prints .coverage file path.

Test run for C:\Users\samadala\tmp\cc-mstest\bin\Debug\netcoreapp2.0\cc-mstest.dll(.NETCoreApp,Version=v2.0)
Microsoft (R) Test Execution Command Line Tool Version 15.8.0-preview-20180605-02
Copyright (c) Microsoft Corporation.  All rights reserved.

Starting test execution, please wait...

Attachments:
 C:\Users\samadala\tmp\cc-mstest\TestResults\ab987d22-bcc9-4748-a04d-071bbe9851c3\samadala_SAMADALA_2018-07-23.18_54_39.coverage

Total tests: 1. Passed: 1. Failed: 0. Skipped: 0.
Test Run Successful.

[codito]

There are two implementation approaches:

• Author msbuild tasks for converting .coverage to .lcov
• Author a vstest logger to convert the .coverage to .lcov

What are the pros and cons? Why is former better than later?

IMHO, second approach would have helped us in the Translation Layer case as well. Imagine someone triggering test run directly on file save (instead of running dotnet watch to do it). We could actually enable a continuous coverage tool.

[smadala]

CoverageLogger looks something similar to https://github.com/smadala/samples/tree/master/CoverageLogger

/cc @mayankbansal018

[harshjain2]

If I have to break down the overall process for converting .coverage to .lcov, these are the steps involved:

1. Convert .coverage to .xml file.
2. [Optional, can be controlled through switch] Read the .xml to read the coverage percentage.
3. Convert .xml file to .locv.

IMHO, we should create vstest logger for achieving 1 and 2.
3 may or may not be part of the same logger.

[codito]

Awesome. Is someone already working on getting the coveragelogger into this repo?

Logger should also involve displaying the information in .lcov.

Please keep everything lcov related in a separate library. Or is there an already existing one we could reuse? I can imagine too many use cases for it ;). E.g. we can later reuse this component to display coverage output for opencover or anyother coverage engine. It can be used for parsing and populating vscode editor too.

[smadala]

Is someone already working on getting the coveragelogger into this repo?

@harshjain2 Has worked on this yesterday. Today I'm planning to work with him and you. To get this to closer.

Please keep everything lcov related in a separate library. Or is there an already existing one we could reuse?

For POC, I'm not much worried on architecture/reusable . If we have proper tests(TDD) we can refactor it later 😄

[codito]

I don't have the required OS to work on this issue.

For POC, I'm not much worried on architecture/reusable . If we have proper tests(TDD) we can refactor it later

Your call :)

[smadala]

I don't have the required OS to work on this issue.

Any time today, drop by my desk, We can do pair programming on my machine 😄

Your call :)

Scoping down everything. We have DEADlines 😄

[codito]

Picking up #27 to complete this.