Will "branch coverage" be included?

I'm wondering whether dotCover will provide branch coverage?

Example:

if (someValue)
{
  // do something
}


If someValue is always true in all tests then the false case is not covered. This is hard to find without branch coverage.

Best regards,
Urs

12 comments
Comment actions Permalink

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

0
Comment actions Permalink

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

1
Comment actions Permalink

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.

1
Comment actions Permalink

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?

1
Comment actions Permalink

Heya!

 

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

2
Comment actions Permalink

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

3
Comment actions Permalink

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.

6
Comment actions Permalink

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).  

1
Comment actions Permalink

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

1
Comment actions Permalink

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

2
Comment actions Permalink

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...

0
Comment actions Permalink

This bug is open since 2010 now. DCVR-234

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

0

Please sign in to leave a comment.