Will "branch coverage" be included?

Hello Urs!
dotCover 1.0 will have only statement coverage.
Branch coverage is scheduled for the next versions.

It's been six years by now. Will branch coverage ever be implemented?

Got a question about this at the booth today as well. Would be nice to have branch coverage e.g. with one-line if statements, null-coalescing operators etc.

Hello dotCover team,

I am using V2018.1.2. I still am do not see branch coverage, only statement coverage is available.

Is there a version in which statement coverage is available?

Heya!

I'm also very much interested in the branch coverage feature. When can we expect it? :)

Is there any chance that dotCover will ever git branch coverage?

We are doing some automated C# code coverage in Azure DevOps and came across this issue.
10 years later is there any chance that something like this will get some attention.

"Branch coverage is scheduled for the next versions." Very keen to know when that "next version" will be.

I would think after 10 years, this should be available or JetBrains should just tell us they are not going to do it (btw, it works in IntelliJ).  

Just ran across this with ternary and null coalescing operators.  It's very misleading.

Hi Ruslan Isakiev, Maarten Balliauw,

Version 1.0 is now a while ago, so 'next versions' should already have happened.

As there are more and more handy branch constructs, this would be a very important feature, otherwise the coverage is very misleading and does not help to ensure a minimum of test coverage for all the different branches of a method.

Could you ask the product owner if this is on the roadmap and when it is planned to come true?

Thank you very much
Michael

Well, just recognized that dotCover claiming a coverage of 99% but Visual Studio Coverage says 93,43% for the same class...

I think the difference is caused by dotCover still does not support branch-coverage? Or there are other reasons that can explain that difference?

Stand-alone app: dotCover 2022.1.20220418.200937

Edit_2022-06-22-15-19: Indeed, dotCover still not supports branch-coverage...

This bug is open since 2010 now. DCVR-234

This is really horrible handling of critical issues and even worse communication. :(

Dear Joel, Harald-René, Michael, Bob, Jlgartee, Oliver, Stefan, Joose, Wish and Edwin.
Thank you for the feedback. The feature request has indeed been shelved for quite a while.
Now it's getting back to the team's roadmap.
The task will require major rework of our key subsystems, so it's hard to provide any ETA at the moment.
But the team is going to start corresponding ground work and prototyping during the next release cycle.

Sounds great. I will continue to use the coverage built into the CI pipeline for now as I have nothing locally that gives branch coverage. Looking forward to this implementation!

Ruslan Isakiev We understand that there is significant effort involved. If you have updated information, even that there is no change at the moment, we would love to follow this.

I'm looking forward for this fix/feature. My company consider to move from Visual Studio to Rider as we see some advantages that stand behind it, but coverage tool is something we use in our daily routine and I can't imagine to use it without branch coverage included. I would be more than happy to see any progress on that topic here.

I like it. I would really make use of that function

Fingers crossed this feature is added soon 😊

I'm currently looking into a possible move from Visual Studio to Rider at my company and I'm wondering how to justify a 13 year old open feature request that is so important to quality after all.

Any update on this, I'm facing coverage issue with null-conditional operators. Related ticket open 5 years ago here.

https://dotnettools-support.jetbrains.com/hc/en-us/community/posts/360000211999-Coverage-after-null-conditional-operators

We are more than halfway through 2024. Is there any branch coverage coming anytime soon?

Hello everyone! We're sorry for the long silence on this matter. Unfortunately, we don't have any updates at this time regarding when the feature will be ready. We appreciate your patience and will keep you updated if there is any news in the future.