Hi,
I'm seeing an issue where the coverage markers just disappear partway through methods:
Partway through the code under test:
External image
Partway through the test code:
External image
These are NUnit tests, and all the tests for this project pass when run manually, in less than a couple of seconds.
I've followed the steps here, but it didn't get any better.
Any ideas?
Andy
Daily Usage Issues
Coverage markers going missing partway through methods
Started by Andy C on 8,075 views
Remco NCrunch Developer
#3856
20 Mar 2013 21:25 UTC
Hi, thanks for posting!
This looks like a mapping/sync issue between the coverage information and the source file.
A known bug exists in 1.44 (and prior) which can cause an issue like this. A fix is pending in the upcoming 1.45 release.
Does a reset (disable/enable) of the engine fix up the coverage alignment? Or is the issue always persistently there?
This looks like a mapping/sync issue between the coverage information and the source file.
A known bug exists in 1.44 (and prior) which can cause an issue like this. A fix is pending in the upcoming 1.45 release.
Does a reset (disable/enable) of the engine fix up the coverage alignment? Or is the issue always persistently there?
Edited 20 Mar 2013 21:25 UTC
Remco wrote:Does a reset (disable/enable) of the engine fix up the coverage alignment? Or is the issue always persistently there?
The issue is persistent, with the caveat that occasionally, I seem to get black dots (which never turn green) instead of no dots.
lol, whilst typing my response, the dots went green! I guess it isn't persistent.
I look forward to 1.45. :-)
Andy
Remco NCrunch Developer
#3860
21 Mar 2013 10:09 UTC
Hi Andy -
The only issues that I currently know of that can produce this kind of effect show themselves only infrequently, so I suspect this may be something new ..
Straight after you've noticed it happening, would you mind submitting a bug report? I'd really like to take a look at the log file.
Cheers,
Remco
The only issues that I currently know of that can produce this kind of effect show themselves only infrequently, so I suspect this may be something new ..
Straight after you've noticed it happening, would you mind submitting a bug report? I'd really like to take a look at the log file.
Cheers,
Remco
Remco NCrunch Developer
#3912
30 Mar 2013 22:16 UTC
For anyone interested, a fix for this problem has been introduced with the newly released version of NCrunch (v1.45).
Post a reply
Log in to reply.