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

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME ...

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.

VS Code Planning mode

After the introduction of Plan mode in Visual Studio , it now also found its way into VS Code. Planning mode, or as I like to call it 'Hannibal mode', extends GitHub Copilot's Agent Mode capabilities to handle larger, multi-step coding tasks with a structured approach. Instead of jumping straight into code generation, Planning mode creates a detailed execution plan. If you want more details, have a look at my previous post . Putting plan mode into action VS Code takes a different approach compared to Visual Studio when using plan mode. Instead of a configuration setting that you can activate but have limited control over, planning is available as a separate chat mode/agent: I like this approach better than how Visual Studio does it as you have explicit control when plan mode is activated. Instead of immediately diving into execution, the plan agent creates a plan and asks some follow up questions: You can further edit the plan by clicking on ‘Open in Editor’: ...

The art of simplicity

Search This Blog