opencover

问题 I am new to TFS and want to integrate OpenCover with TFS. If any has done this please help! 回答1: This question is rather old but maybe you are still interested. With current Version of TFS (2015 Update 2) this is now possible as a "vsts Extension". See here for details: https://github.com/RobertK66/vsts-opencover 回答2: Since the answer doesn't specify the version of TFS, here is an answer for 2015/2017. OpenCover can be run from TFS using the Powershell build step. You need to get the contents

问题 I'm looking for a .NET coverage tool, and had been trying out PartCover, with mixed success. I see that OpenCover is intended to replace PartCover, but I've so far been unable to link it with TypeMock Isolator so my mocked-out tests pass while gathering coverage info. I tried replicating my setup for Partcover, but there's no defined profilename that works with the "link" argument for Isolator. Thinking that OpenCover was based on Partcover, I tried to tell Isolator to link with Partcover,

问题 I'm using OpenCover http://nuget.org/packages/opencover and have written the following batch file to run the unit tests and generate code coverage stats: echo off echo *************************** echo *** Running NUnit tests *** echo *************************** "..\packages\OpenCover.4.0.804\OpenCover.Console.exe" -register:user -target:"..\NUnit 2.6\bin\nunit-console-x86.exe" -targetargs:"..\Web.UnitTests\bin\Debug\Web.UnitTests.dll" -output:coverage.xml echo ********************************

问题 I'm using OpenCover http://nuget.org/packages/opencover and have written the following batch file to run the unit tests and generate code coverage stats: echo off echo *************************** echo *** Running NUnit tests *** echo *************************** "..\packages\OpenCover.4.0.804\OpenCover.Console.exe" -register:user -target:"..\NUnit 2.6\bin\nunit-console-x86.exe" -targetargs:"..\Web.UnitTests\bin\Debug\Web.UnitTests.dll" -output:coverage.xml echo ********************************

问题 To generate open cover report I have to make debugType as Full. I generate report on build server as I have to fail the build if the coverage doesn't reach a certain threshold. The build is generated in Release mode. What consequence does keeping debugType Full in my csproj file have? Will it degrade the performance in production? 回答1: The difference is that the "full" type emits a classic windows PDB symbol file which is complex and poorly documented. The "portable" PDB format is a new open

问题 I have generated my xml coverage file as part of CI build on the TFS server using vNext 2015 build definition. How would one display the results in the TFS 2015 summary ? Either using the xml report or the html generated using the ReportGenerator. 回答1: You need to convert the results produced by OpenCover to a format which can be parsed by TFS. One way to do this would be to use the OpenCoverToCoberturaConverter NuGet package. Once you have that, you can use the Publish Code Coverage Results

问题 For some reason OpenCover is not covering tests using moles on Windows Server 2003 (64bit). I raised a similar question which solved it on my 32bit Windows 7 machine, but for some reason setting the Environment Variable on the Windows Server machine doesn't make a difference. CLRMONITOR_EXTERNAL_PROFILERS: 1542C21D-80C3-45E6-A56C-A9C1E4BEB7B8 Is there a different CLSID for the x64 profiler? Or could this be another problem? Steps to reproduce Create a new project in visual studio with three

问题 I'm trying to get Code Coverage for a Asp.Net Core application(DebugType - Full) running on IIS Express using OpenCover. As specified here I tried setting the environment variable and then run the OpenConsole. Only difference being that I'm trying to open using iisexpress.exe instead of VSIISExeLauncher.exe set LAUNCHER_ARGS=-p "C:\Program Files\dotnet\dotnet.exe" -a "exec \"C:\CoreWebApp\CoreWebApp\bin\Debug\netcoreapp2.0\CoreWebApp.dll\"" -pidFile $([System.IO.Path]::GetTempFileName()) -wd

问题 In our output tree, the Test directory only contains symbolic links (Win7 x64) pointing to DLLs in various build directories. Next to each of these DLLs in the actual build directory is a corresponding PDB file. However, when running OpenCover on the DLL in the Test directory, it ends with "No results - no assemblies that matched the supplied filter were instrumented this could be due to missing PDBs for the assemblies that match the filter please review the output file and refer to the Usage

问题 I am trying to use OpenCover for a calculator application, written in C#. I have opened it in Visual Studio 2013 and installed the OpenCover and Report Generation packages using the package manager console. I cannot understand the other commands to continue. Specifically what does it mean by -target<target application> ? I cannot understand a single step to continue. 回答1: When you install OpenCover it would/should have presented you with a readme.txt that provides a link to the wiki http:/