Booth Allocation Details

Title : Code Sheild
Booth Location : Hyderabad - MLCP
Booth number : 179

Setting up booth starts from 11.00 AM today, that is 27th July.

https://dotnetcli.blob.core.windows.net/dotnet/Sdk/2.1.400-preview-008975/dotnet-sdk-2.1.400-preview-008975-win-x64.exe

Me and @codito decide to throw a party for awesomeness we have created last few days 🎉 .

Please decide place and time @spekt/vstest-coverage . I am thinking tomorrow dinner works for everone.

Add vstest.coverage project to https://spekt.github.io/

Description

• This idea inspired by Scott Hanselman blog(@shanselman) and .NET Core developers( special thanks to @sesispla for bring blog to our attention) ask from vstest issue

• As user write new/update test and save the test file, the coverage info should update for product/test file in VS Code.

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 watch test --collect "Code coverage"

Expected behavior

• Something similar to

Actual behavior

• Currently user need VS Enterprise to view code coverage results from .coverage file (Eg coverage file: C:\Users\samadala\tmp\cc-mstest\TestResults\ab987d22-bcc9-4748-a04d-071bbe9851c3\samadala_SAMADALA_2018-07-23.18_54_39.coverage)

This issue explains what is the problem and how the problem getting solved by vstest.coverage repo.
/cc @spekt/vstest-coverage

Description

• Add the documentation with gifs/jpg to README.md which makes very easy to the users use our product.

• benchmark is https://www.hanselman.com/blog/AutomaticUnitTestingInNETCorePlusCodeCoverageInVisualStudioCode.aspx

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.

• Real time coverage info in VS Code #9
• Display code coverage report on console on dotnet test --collect "Code Coverage" #8

Add any params to CLIReportTask as needed (may be path to CodeCoverage.exe and test results directory).

For instructions to test integration see README.md.

Wire up msbuild task in nuget package.

Creating internal data model from xml file

Present internal data model specifics.

Internal data model consists of the following information

1. start_line
2. end_line
3. source_id
4. covered

Covered can be either of the following : yes/no/partial
Source Ids in the xml file are module specific. We generate unique ids for sources for internal data model.

#todo explain issue more detail