Skip to main content

Discovering Visual Studio 2026 – Code coverage

Yes! The new Visual Studio 2026 edition is available in preview (now called Insiders). I'll take some time this week to walk through some of the features I like and maybe some of the rough edges I discover along the way.

Today I want to take a look at Code Coverage in Visual Studio. “Wait… what?!” I here you think, “Code coverage is not a new feature in Visual Studio.”. And yes you are right, But until this version Code Coverage was only available for the Enterprise Edition of Visual Studio.

With Visual Studio 2026, it is finally a part of the Community and Professional Edition as well. (I always thought it was strange to call yourself professional but don’t focus on code coverage.)

How to use Code Coverage in Visual Studio

So, if you never had the opportunity to use the Code Coverage feature in Visual Studio, let me walk you through the steps.

Go to the Test menu and select the Analyze Code Coverage for All Tests option from the menu.

Another option is to right click on a set of tests in the Test Explorer and select the Analyze Code Coverage option from the context menu.

Once the code coverage analyzer has completed its job, you can see the results on the Code Coverage Results window.

Here you can see the coverage percentage on Assembly, Class and Method level.

The coverage percentage can also be highlighted in the editor making it really easy to identify what parts of your code are still missing tests. Therefore, click on the Show Code Coverage Coloring icon in the Code Coverage Results window:

 

I’m really happy that this feature finally made it into all editions.

More information

Determine code testing coverage - Visual Studio (Windows) | Microsoft Learn

Labels:

Popular posts from this blog

.NET 8–Keyed/Named Services

A feature that a lot of IoC container libraries support but that was missing in the default DI container provided by Microsoft is the support for Keyed or Named Services. This feature allows you to register the same type multiple times using different names, allowing you to resolve a specific instance based on the circumstances. Although there is some controversy if supporting this feature is a good idea or not, it certainly can be handy. To support this feature a new interface IKeyedServiceProvider got introduced in .NET 8 providing 2 new methods on our ServiceProvider instance: object? GetKeyedService(Type serviceType, object? serviceKey); object GetRequiredKeyedService(Type serviceType, object? serviceKey); To use it, we need to register our service using one of the new extension methods: Resolving the service can be done either through the FromKeyedServices attribute: or by injecting the IKeyedServiceProvider interface and calling the GetRequiredKeyedServic...
Read more

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.
Read more

Kubernetes–Limit your environmental impact

Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...
Read more