Conversation
mayankbansal018
requested review from
PBoraMSFT,
cltshivash,
pvlakshm and
singhsarab
| @@ -0,0 +1,17 @@ | |||
| # Syntax | |||
| ```vstest.console.exe --collect:"code coverage"``` or ```dotnet test --collec:"code coverage"``` | |||
There was a problem hiding this comment.
Also the name of the file. codecoverage*
|
|
||
| # Output | ||
|
|
||
| A coverage file, which contains detailed report on what all code was hit when unit tests were run for specific(s) project. The generated file can be viewed in Visual Studio Enterprise, for a detailed analysis. |
|
|
||
| * We have often observed failures/crashes when tests are run with Code Coverage enabled on Windows 8.1(&Lower), or Windows Server 2012(& Lower), failing with ```Access Violation in covrun32.dll``` | ||
|
|
||
| For such issues we recommened users to use coverage configuration specified at https://github.com/Microsoft/vstest/blob/master/src/DataCollectors/TraceDataCollector/VanguardCollector/DefaultCodeCoverageConfig.xml |
| @@ -0,0 +1,17 @@ | |||
| # Syntax | |||
There was a problem hiding this comment.
What about /enablecodecoverage or via settings?
Make it clear by adding one liner that this doc is related to the specified syntax
|
|
||
| * Coverage file fails to open in VS E.g. https://github.com/Microsoft/vstest/issues/1814 | ||
|
|
||
| One of the possible reason for this is when there are too many blocks in a single function. Currently we support ```65535(USHRT_MAX)``` blocks in a single method, beyond that we go into serialization issue while reading this data from coverage file. |
There was a problem hiding this comment.
What is the recommendation here?
Also, I see some folks reported the Shimdll issue, or related to verifiable, should we cover that as well ?
pvlakshm
left a comment
pvlakshm
left a comment
There was a problem hiding this comment.
What prompted the creation of this doc? I think I may be missing some context here, hence I ask.
Is this already an exhaustive list of all known issues?
BTW, there is a spelling mistake in the name of the .md file.
|
@mayankbansal018 Are planning to take this anytime soon ? |
|
@AbhitejJohn probably yes. Will let @jakubch1 decide what to do with this next. |
6 participants
No description provided.