Say I have some specflow tests and I start one wit the debugger and have a breakpoint in the code (not in the specflow test). When the break point is hit if I step over until eventually control returns to the specflow test then I almost always get an EngineExecutionException at the point the debugger tries to go to the specflow .feature file and vs sort of locks up and I have to kill all of the NCRunch processes to get VS to allow the debugger to restart
Any ideas?
Build/Test Issues
Engine execution exception when debugging through Specflow tests
Started by samholder on 6,324 views
Remco NCrunch Developer
#6070
22 Jun 2014 22:19 UTC
Hi,
Thanks for sharing this issue. I've been quickly able to recreate it in exactly the manner you described.
The issue also appears outside of NCrunch, when performing the same actions with any other test runner. This suggests the issue is something with SpecFlow or the CLR itself. My understanding is that the ExecutionEngineException is generally caused by problems outside managed code.
Perhaps you could raise this issue with SpecFlow and see if they have a solution for it?
Cheers,
Remco
Thanks for sharing this issue. I've been quickly able to recreate it in exactly the manner you described.
The issue also appears outside of NCrunch, when performing the same actions with any other test runner. This suggests the issue is something with SpecFlow or the CLR itself. My understanding is that the ExecutionEngineException is generally caused by problems outside managed code.
Perhaps you could raise this issue with SpecFlow and see if they have a solution for it?
Cheers,
Remco
Post a reply
Log in to reply.