If you haven’t setup your .Net Core project/s for code coverage instrumentation, see my previous post: Part 1: .Net Core Project Setup – Code Coverage.
That said, let’s go through the settings for enabling code coverage in VSTS builds. The basic structure of CI build definition would be:
- Build the application
- Run Tests (Unit Tests with Code Coverage)
- Publish Artifacts
In this post, I’ll skip over using NUnit as a test framework for .Net Core. For using NUnit as a test framework, see my previous post: Using NUNIT Test Framework do validate deployments in VSTS Release Management
Note from the image above that we’ve disabled the Dotnet test task because code coverage is currently not supported on dotnet.exe CLI (as of writing of this post)
However, vstest.console.exe does support code coverage. This is the task we’ve enabled to run our unit tests for code coverage instrumentation as well as running the tests from NUnit written code. Vstest.console.exe automatically detects NUnit tests since part of the restore nuget package includes the NUnit test adapters.
The important note here is to ensure that you properly setup the vstest task in the build definition and it’s settings:
- Ensure that you have code coverage enabled option
- Ensure that you are pointing to the .runsettings file for further code coverage settings
- Install the NUnit adapters as part of your test project
Running the build yields the following result.
At this point, you can download the code coverage file and open the result in Visual Studio for further inspection.
You may have noticed that in my build, I also have tasks for SonarQube. What is SonarQube and why use it? For this, see part 3 (final) post for this series: Part 3: VSTS SonarQube Build Task