NET Core applications, we need to use a task to run dotnet test. Run tests and collect code coverage results We need to add two steps to our YAML file: one for collecting the code coverage on test projects, and one for actually publishing it.

Once we have Coverlet installed, it's time to add the code coverage evaluation to the CI pipeline. So, running a simple dotnet add package coverlet.msbuild on your test projects is enough! Create YAML tasks to add code coverage This package must be installed in every test project in your Solution. Then, in the second part of this article, we're gonna see how to view the coverage history on your Azure DevOps dashboard, by using a plugin called Code Coverage Protector.īut first, let's start with the YAML pipelines! Coverlet - the NuGet package for code coverageĪs already explained in my previous article, the very first thing to do to add code coverage calculation is to install a NuGet package called Coverlet. This simple addition will help you see the status of a specific build and, if it's the case, update the code to add more tests. In this article, we're gonna see how to show that report on Azure DevOps: by using a specific command (or, even better, a set of flags) on your YAML pipeline definition, we are going to display that report for every build we run on Azure DevOps. In a previous article, we've seen how to use Coverlet and Cobertura to view the code coverage report on Visual Studio (of course, for. Code coverage is a good indicator of the health of your project: the more your project is covered by tests, the lesser are the probabilities that you have easy-to-find bugs in it.Įven though 100% of code coverage is a good result, it is not enough: you have to check if your tests are meaningful and bring value to the project it really doesn't make any sense to cover each line of your production code with tests valid only for the happy path you also have to cover the edge cases!īut, even if it's not enough, having an idea of the code coverage on your project is a good practice: it helps you understanding where you should write more tests and, eventually, help you removing some bugs.

Visual studio code coverage