You must add Coverlet.msbuild to every test project in your solution. The first thing to do to add code coverage reports to our project is to install Coverlet, a NuGet package, whose documentation can be accessed on GitHub. The code and the tests are pretty straightforward but have we really covered the Replace method with enough tests to be sure not to have missed something? Coverlet - the NuGet Package for code coverage I think the MSDN page needs updating.Public class MyArrayTests This had me stumped for a while, but I'm glad it's fixed. It turns out the regular expression parser is being confused by the non-escaped dots (cheers Grin), so I need to do this instead. Make sure the tests ran, required binaries were loaded, had matching symbol files, and were not excluded through custom settings. runsettings file:īut instead of basking in the glory of a 100% code coverage score, I get the following error:Įmpty results generated: No binaries were instrumented. Following the guide over at the MSDN suggests that you can do the following in a. The alternative is to exclude the whole assembly. You can apply the attribute to every test class, and that works fine, but is a right faff with lots of tests. The only problem I've discovered with this is by default the Code Coverage tool will analyse all projects in the solution including the test projects themselves, which score 0% coverage and skews your solution stats. I keep tests in their own projects, named after the assembly they are testing, but with '.Tests' bunged on the end. I recently started playing with Visual Studio's code coverage analysis tool to show me where my unit testing is insufficient.

Visual studio code coverage not working