Making it cross platform is on the radar, and may even be supported by the time you read this.Code coverage testing is an important measure that quantifies the degree to which the source code of the program has been tested. It's unfortunately still Windows-only, but they have removed the requirement for Visual Studio Enterprise. csproj, and me explaining about the new vs the old pdb (Program DataBase) debug information file.įortunately, as of September, there is a new parameter to dotnet test: -collect 'Code Coverage'. Then, it would require adding a test adapter, fixing a bug with the tool path, adding a referencing the Microsoft.CodeCoverage NuGet package, adding a Full line to the main. Task dependency management++īefore Visual Studio 15.8, getting coverage would have involved switching to the windows-only alternative and requiring Visual Studio Enterprise. This isn't really any different than any 'AKE' tool like Make, Psake, Rake, or MS Build, but it's a nice benefit over bash or Powershell scripts where you'd have to use global state. In that case Cake is smart enough to only build once if I run Deploy. Vendor Neutral (could easily switch to Jenkins or Team City).And if you've read my previous articles (or videos) about why Cake is such a fantastic tool for automating a devops pipeline, then you know how I propose to approach the devops problem. If you read my last blog post on the importance of calculating code coverage from a team perspective you know what code coverage is and why I care so much. The tech stack on my new project looks like this:īut wait, before I alienate my audience down to zero readers, let me back up a little, bear with me. I was going to explain the many steps I went through to calculate what seems like a fairly basic metric.īut instead, I'm going to tell you how much happier your life can be. Originally, this was the story of the pain involved me starting a new project recently based on Microsoft's new, modern, cross-platform tech stack. Fortunately, as of last month and Visual Studio 15.8, generating the metric is easy. A couple of months ago calculating code coverage on the command line was quite challenging in ASP.Net Core.

Visual studio code coverage cl