Vstest: Code Coverage enabled breaks reporting

[MoiMoiDG]

Description

IMPORTANT: if the defect is reproduced only in a workflow from within the Visual Studio IDE then do not report the issue here - instead, please report it using Visual Studio's "Send Feedback" option that can be accessed from the Help menu OR using this link https://developercommunity.visualstudio.com.

For a defect reproducable from the vstest command line, describe the issue you've observed.

In TFS 2018.2 CI build, enabling code coverage breaks reporting of test results (and code coverage itself).

Steps to reproduce

What steps can reproduce the defect?
Please share the setup, commandline for vstest.console, sample project, target
framework etc.

TFS 2018.2, code coverage enabled. See details below.

Expected behavior

Share the expected output

Enabling code coverage shall show the code coverage, disabling it shall not compute it or hide the results.

Actual behavior

What is the behavior observed?

Enabling code coverage breaks test results.

Diagnostic logs

Please share test platform diagnostics logs. Instructions to collect logs are here.
The logs may contain test assembly paths, kindly review and mask those before sharing.

Code Coverage enabled, see screenshot below:

Code Coverage disabled, see screenshot below:

Logs, see attachment below:
13_Test Assemblies release.Tests.dll;-obj.txt

Environment

Please share additional details about the test environment.
Operating system, Build version of vstest.console

TFS 2018.2, see attached logs for more details. Let me know whether more information is needed.

[ShreyasRmsft]

@MoiMoiDG take a look at issue https://github.com/nunit/nunit3-vs-adapter/issues/519

Nunit does not support running tests with code coverage run while using the vstest platform tool installer.

[MoiMoiDG]

@ShreyasRmsft: Thank you for the reply. I had a look at the linked issue, but I could not find any information to solve my problem.

[ShreyasRmsft]

@MoiMoiDG as of now this hasn't been fixed. We have to go fix it in the Nunit adapter. Until then you may want to use VS instead of the vstestplatformtool installer for running Nunit tests with code coverage

[ShreyasRmsft]

@MoiMoiDG please follow the workaround for now. Will track the issue in the one filed on the NUnit Adapter side

[MoiMoiDG]

@ShreyasRmsft: Thanks for the reply. I understand to keep the other issue open, but the workaround is not that easy for me, because I would need VS Enterprise on each machine running the tests. Is there any other solution but switching from NUnit to MS Test?