Welcome Guest! To enable all features please Login or Register.

Notification

Icon
Error

Test Coverage Differernces
craigber
#1 Posted : Monday, April 16, 2018 1:00:32 PM(UTC)
Rank: Newbie

Groups: Registered
Joined: 3/22/2016(UTC)
Posts: 4
Location: United States of America

I'm getting different test coverage metrics from NCrunch vs. VS Test. NCrunch is reporting 63% test coverage while VS is reporting 71%. This is VS 2017 and NUnit 3. All unit tests are passing. Any ideas why these would be different?
Remco
#2 Posted : Monday, April 16, 2018 11:08:58 PM(UTC)
Rank: NCrunch Developer

Groups: Administrators
Joined: 4/16/2011(UTC)
Posts: 7,123

Thanks: 957 times
Was thanked: 1286 time(s) in 1193 post(s)
Hi, thanks for posting.

There are differences in how VS and NCrunch capture and process coverage information. NCrunch has a lower resolution in that it captures coverage line-by-line rather than statement-by-statement. This is done for performance and complexity reasons.

However, I don't think this would account for such a large difference, and it would usually result in the code coverage being higher under NCrunch than under VS.

It's hard for me to say why this is different without being able to do a side-by-side comparison. I recommend drilling down into your code to identify the differences. It may be the result of an ignored test or a difference in runtime behaviour.
Users browsing this topic
Guest
Forum Jump  
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.

YAF | YAF © 2003-2011, Yet Another Forum.NET
This page was generated in 0.022 seconds.
Trial NCrunch
Take NCrunch for a spin
Do your fingers a favour and supercharge your testing workflow
Free Download