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

Notification

Icon
Error

Ncrunch doesn't seem to be highlighting the start of tests in scenario outlines in feature files
samholder
#1 Posted : Thursday, July 7, 2016 8:53:46 AM(UTC)
Rank: Advanced Member

Groups: Registered
Joined: 5/11/2012(UTC)
Posts: 94

Thanks: 28 times
Was thanked: 12 time(s) in 12 post(s)
I don't know if this is a regression or not, but I added a fix to specflow to include an additional #line pragma which enabled the starting markers to show up in the feature files when using scenario outlines: https://github.com/techtalk/SpecFlow/pull/372

I've noticed that this is no longer working with the latest version of ncrunch in VS2015. When I check with the same version of NCrunch in 2013 I get the markers by the examples allowing me to start the tests. When I check in VS2015 I don't see the markers. I checked with 2.20.04 in both after noticing when I had 2.23.03 installed for VS2015, in case it was an issue in a newer version.

I havn't checked in the lastest version with VS2013, but will try and do that today.

Remco
#2 Posted : Thursday, July 7, 2016 10:30:58 AM(UTC)
Rank: NCrunch Developer

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

Thanks: 959 times
Was thanked: 1290 time(s) in 1196 post(s)
Hi Sam,

Can you confirm that this is a regression in 2.23? 2.23 did introduce some very significant internal changes around how code coverage is handled. It's possible that it no longer allows a test to start on a line that isn't reported as covered code by the test. If this is indeed the case, I may need to change the behaviour in the coverage indexing.
1 user thanked Remco for this useful post.
samholder on 7/7/2016(UTC)
samholder
#3 Posted : Thursday, July 7, 2016 1:30:07 PM(UTC)
Rank: Advanced Member

Groups: Registered
Joined: 5/11/2012(UTC)
Posts: 94

Thanks: 28 times
Was thanked: 12 time(s) in 12 post(s)
Hi, I've just updated my VS2013 to the latest build and can confirm that the markers show in 2013 but not in 2015, so not sure if this is a regression or a change in behaviour between versions of VS or because the VS integration of Specflow has been updated for 2015. Leave it with me for now whilst I investigate the last option as I'm suspecting that at this point in time.
1 user thanked samholder for this useful post.
Remco on 7/7/2016(UTC)
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.024 seconds.
Trial NCrunch
Take NCrunch for a spin
Do your fingers a favour and supercharge your testing workflow
Free Download