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

Notification

Icon
Error
Cast operators
Options
Previous Topic Next Topic
SvenL
#1 Posted : Friday, February 2, 2018 9:35:15 AM(UTC)
Rank: Newbie

Groups: Registered
Joined: 2/2/2018(UTC)
Posts: 2
Location: Netherlands
It looks like NCrunch can't find the tests I wrote for my Cast-operators (both implicit as explicit) and thus the markers stay white/black.
Back to top
Remco
#2 Posted : Friday, February 2, 2018 11:09:01 PM(UTC)
Rank: NCrunch Developer

Groups: Administrators
Joined: 4/16/2011(UTC)
Posts: 6,976

Thanks: 930 times
Was thanked: 1257 time(s) in 1170 post(s)
Hi, thanks for posting.

Do other test runners also find these tests? Is it possible you've ignored them using the 'Ignore' button in the Tests Window?

Do newly created tests of the same structure also stay undiscovered by NCrunch? If so, are you able to share a sample declaration of any of these tests?
Back to top
SvenL
#3 Posted : Tuesday, February 6, 2018 6:42:19 AM(UTC)
Rank: Newbie

Groups: Registered
Joined: 2/2/2018(UTC)
Posts: 2
Location: Netherlands
It was a naming issue. NCrunch did find them after renaming one.
It is a pity that NCrunch does not report this kind of problems a little more verbose; it finds the test but can't 'handle' it... im(h)o this is a real issue and the user should be notified.
Also after finding this issue, finding the underlying cause can be a real problem particularly when using NUnits TestCase / TestCaseSource or xUnits Theory, this can sometimes be real effort.

Thanks for pointing me in the right direction.
Back to top
Remco
#4 Posted : Tuesday, February 6, 2018 11:50:54 AM(UTC)
Rank: NCrunch Developer

Groups: Administrators
Joined: 4/16/2011(UTC)
Posts: 6,976

Thanks: 930 times
Was thanked: 1257 time(s) in 1170 post(s)
SvenL;11743 wrote:

It is a pity that NCrunch does not report this kind of problems a little more verbose; it finds the test but can't 'handle' it... im(h)o this is a real issue and the user should be notified.


I'm sorry to hear of the frustration here. I agree that this is a scenario that we would ideally like to avoid. Are you able to share any more information about how the naming caused this problem? Catching these sorts of issues can be difficult as it often depends on how the test framework reports the information, but if there's a way to make it more obvious in NCrunch then I'd like to look into this.
Back to top
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.030 seconds.
Trial NCrunch
Take NCrunch for a spin
Do your fingers a favour and supercharge your testing workflow
Free Download