Hello. Excuse me for my closed issues with dumb questions, i just recently opened for me OpenCover.UI and want to get it right.
Can you help me to find instruction how to launch this project on VS2015? I need to get my .vsix-file after the starting this solution by my Visual Studio 2015, but i don't know, what project in this solution i have to set as autorun project.
How this project can know what lines are covered by unit-tests?
I mean, before it highlight the line it has to know what lines are covered by test.
I see that %localappdata%\Apps\OpenCover\OpenCover.Console.exe find this stuff, but i'm interesting in code realisation. If anyone has a time for this dumb question, please, answer.
This may not be the right platform but I'm having difficulty getting CodeCoverage reports when running .NET Core Unit tests with codecov.
I have installed all the required packages and running it runs the test with xUnit nicely. I have also installed OpenCover and got that to work. I am still trying to generate the .xml and I can't figure out where I'm going wrong, or how to fix it!
The command line I'm running boils down to
$ C:/Users/pkErbynn/.nuget/packages/opencover/4.7.922/tools/OpenCover.Console.exe -register:user -target:"C:/Users/pkErbynn/.nuget/packages/xunit.runner.console/2.4.1/tools/net46/xunit.console.x86.exe" -targetargs:"C:/Users/pkErbynn/source/repos/cross-cov/CrossroadsUnitTests/bin/Debug/netcoreapp3.1/CrossroadsUnitTests.dll -noshadow" -output:"./coverage.xml" -filter:"+[Crossroads*]* -[CrossroadsUnitTests*]*"
The command runs, then in the console, I see this...
Executing: .\packages\xunit.runner.console\2.4.1\tools\net46\xunit.console.x86.exe xUnit.net Console Runner v2.4.1 (32-bit Desktop .NET 4.6, runtime: 4.0.30319.42000) System.IO.FileNotFoundException: Could not load file or assembly 'System.Runtime, Version=184.108.40.206, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified. Committing... No results, this could be for a number of reasons. The most common reasons are: 1) missing PDBs for the assemblies that match the filter please review the output file and refer to the Usage guide (Usage.rtf) about filters. 2) the profiler may not be registered correctly, please refer to the Usage
Can you please suggest where I'm going wrong? I've been beating my head against the wall for weeks on this.
Thanks you in advance.