This repository has been archived by the owner on Dec 5, 2022. It is now read-only.
Document known CC issues #160
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
mayankbansal018
requested review from
pvlakshm,
cltshivash,
singhsarab and
PBoraMSFT
singhsarab
suggested changes
Oct 23, 2018
| @@ -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
reviewed
Oct 24, 2018
|
@mayankbansal018 Are planning to take this anytime soon ? |
|
@AbhitejJohn probably yes. Will let @jakubch1 decide what to do with this next. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.