Comments on: Debugging Cuke4Nuke Step Definitions

By: Cucumber Tip: IRB From Inside a Step Definition | The Agile Radar

Cucumber Tip: IRB From Inside a Step Definition | The Agile Radar — Thu, 08 Dec 2011 08:16:02 +0000

[...] Related posts:Debugging Cuke4Nuke Step Definitions [...]

By: flores

flores — Thu, 14 Apr 2011 13:43:51 +0000

1. I added in step [Before] decorated method

#if DEBUG
Debugger.Break();
#endif

2. Then when I ran Cuke4Nuke … form command line I by OS that:
“Application Server met breakpoint…”
Then OS displayed a dialog named “Application Server has stopped working…” with “Debug” button

3. Clicking on the button I was able to attach VS debugger to Cuke4Nuke.Server.exe

4. Next I was able to debug what I wanted (including G/W/T parameters passed from features files)

cuke4nuke: 0.4.0
cucumber: 0.10.2
ruby: 1.9.2
OS: W7/64

By: Stefan Dobrev

Stefan Dobrev — Thu, 04 Feb 2010 19:53:43 +0000

My bad. You are absolutely right. It does not work. Despite the user defined breakpoint that is created by the call to Debugger.Break() the Cuke4Nuke server continues its execution and exits.

By: Richard

Richard — Wed, 03 Feb 2010 08:18:01 +0000

@Stefan – Have you tried this in a Cuke4Nuke step definition? With Cuke4Nuke.Server.exe not having debug symbols and loading step definition assemblies via reflection, I wonder if it will work.

By: Stefan Dobrev

Stefan Dobrev — Sun, 31 Jan 2010 18:40:04 +0000

You can use Debugger.Break() in your .NET code when you want to break and attach a debugger.

By: Matt Wynne

Matt Wynne — Thu, 14 Jan 2010 07:13:48 +0000

Neat trick Richard!

I think the way to build debugging into Cuke4Nuke would be to use the /DebugExe command-line switch for of VS: http://www.olegsych.com/2007/08/debugexe-command-line-switch-in-visual-studio/

By: Aslak Hellesøy

Aslak Hellesøy — Thu, 14 Jan 2010 00:21:15 +0000

I love this idea. The exact same approach can be taken with Cuke4Duke. I have linked to your article from here:

http://wiki.github.com/aslakhellesoy/cuke4duke/debug-cuke4duke-steps

By: Richard

Richard — Wed, 13 Jan 2010 17:28:14 +0000

@Luke – Good idea. I think debugging support should be built into Cuke4Nuke somehow, but I’m not sure exactly how. Right now, I don’t ship symbols in the gem, so just giving time to attach to the debugger only solves half the problem.

If you come up with a good debugging solution, I’d be glad to pull it.

By: Luke Smith

Luke Smith — Wed, 13 Jan 2010 13:25:49 +0000

I’ve debugged tests with Cuke4Nuke by running Cuke4Nuke via Visual Studio. In the Server project settings I added the relevant command line arguments (in the Debug tab). F5 the server, then run cucumber separately. It’s fiddly since you have to find the right place to step into your test code. Not really a nice solution

Could you add a debug flag to Cuke4Nuke? When it’s present it won’t run cucumber until some user action in the console. This would give time to attach a debugger to the process. What do you think? Seems like a slightly less hacky approach. I might give it a go one evening this week.

By: Declan Whelan

Declan Whelan — Wed, 13 Jan 2010 03:03:27 +0000

Very clever!