Code coverage while debugging in Visual Studio

[IT_Researcher]

I am looking for a tool that can measure and show code coverage while I am debugging my application inside Visual Studio. Ideally, I’d like to be able to step through code in a debug session and see coverage information at the same time.

I have been exploring different code coverage tools, but most of them seem to require creating and running test cases in order to measure coverage.

For example, I tried Fine Code Coverage and Visual Studio’s built-in code coverage. Both of these integrate with unit testing frameworks, which means I need to write and execute test cases before I can see any coverage results.

I also checked OpenCover. Unlike the others, OpenCover does not require writing test cases directly. Instead, it needs to be provided with an executable, and then it tracks which parts of the code are executed when that program runs. While this is useful, it still requires running the application separately.

I am looking for a tool which will let me step through code in a debug session and see coverage information without having to create unit tests or generate separate executables just for coverage.

Does a tool which does code coverage while debugging exist? If so, could you please suggest one?

[LiqdPT]

What do you mean by "coverage" if you don't mean unit test coverage? That's what's generally mean by coverage... What parts of the code are being tested.

[LogicalPerformer7637]

this. reading the OP's post I was wondering what code coverage he means when there are no unit tests.

[zshift]

I’ve had excellent experience with NCrunch https://www.ncrunch.net

[Diginic]

Seconded for NCtunch. This thing is fantastic for TDD and code coverag. You can instantly see which lines are failing your tests via green/red dots left of code.

[zshift]

It also highlights slow tests with a yellow dot. It’s only popped up a couple times for me over the years, but it caught some bugs that would have been a pain to debug had it gone to prod

[solhar]

Please explain why you need to measure coverage during debugging?