Debugging Cucumber Feature from IntelliJ

[Amiruddin Nagri]

I am trying to debug Cucumber feature from IntelliJ, but it crashes as soon as it starts. Did anyone else tried it ?

I also tried debugging the spec using ruby-debug and inserting debugger command in step definitions, the debugger stops as soon as it encounters the breakpoint, but when I do list it fails with a very long stack trace. Again has anyone tried it ?

Or if these are known bugs ?

Regards,
Amiruddin Nagri,
Bangalore, 560008, KA
India

Y! IM : amir_...@yahoo.com
GTalk : amir....@gmail.com

[Jon Kern]

did you try searching/posting this on jetbrains forum?

jon
blog: http://technicaldebt.wetpaint.com
twitter: http://twitter.com/JonKernPA

Amiruddin Nagri said the following on 8/4/10 6:47 AM:

--
You received this message because you are subscribed to the Google Groups "Cukes" group.
To post to this group, send email to cu...@googlegroups.com.
To unsubscribe from this group, send email to cukes+un...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/cukes?hl=en.

[Amiruddin Nagri]

Since I was getting similar behavior when debugging it manually using ruby-debug, I think the main problem is when you try to issue command list to get your position in stack when debugging. Probably IntelliJ would be doing same to display the stack in visual form and crashing.

Doesn't anyone use debugging tools when troubleshooting cucumber specs ?

Regards,
Amiruddin Nagri,
Bangalore, 560008, KA
India

Y! IM : amir_...@yahoo.com
GTalk : amir....@gmail.com

[Matt Wynne]

On 5 Aug 2010, at 07:22, Amiruddin Nagri wrote:

Since I was getting similar behavior when debugging it manually using ruby-debug, I think the main problem is when you try to issue command list to get your position in stack when debugging. Probably IntelliJ would be doing same to display the stack in visual form and crashing.

Doesn't anyone use debugging tools when troubleshooting cucumber specs ?

Sometimes, but not very often. I normally nail things down with a unit test when I don't understand what's going in in the features.

Maybe it's your ruby version? Try asking on the ruby mailing list.

cheers,
Matt

http://blog.mattwynne.net

+44(0)7974 430184

[Amiruddin Nagri]

Matt, I also do the same.

Basically I am preparing a presentation about BDD and cucumber, and one of the issues I have faced while using cucumber was this debugging issue.
I want to verify if anyone else is facing the same issue before I present it as things to look out for when using cucumber.

Also, any inputs regarding my presentation are most welcome.

-Amir

[Phillip Koebbe]

>> Y! IM : amir_...@yahoo.com <mailto:amir_...@yahoo.com>
>> GTalk : amir....@gmail.com <mailto:amir....@gmail.com>

>>
>>
>>
>> On Thu, Aug 5, 2010 at 6:42 AM, Jon Kern <jonk...@gmail.com
>> <mailto:jonk...@gmail.com>> wrote:
>>
>> did you try searching/posting this on jetbrains forum?
>>
>> jon

>> blog:http://technicaldebt.wetpaint.com <http://technicaldebt.wetpaint.com/>

>> twitter:http://twitter.com/JonKernPA
>>
>>
>> Amiruddin Nagri said the following on 8/4/10 6:47 AM:
>>>
>>> I am trying to debug Cucumber feature from IntelliJ, but it
>>> crashes as soon as it starts. Did anyone else tried it ?
>>>
>>> I also tried debugging the spec using ruby-debug and
>>> inserting debugger command in step definitions, the debugger
>>> stops as soon as it encounters the breakpoint, but when I do
>>> list it fails with a very long stack trace. Again has anyone
>>> tried it ?
>>>

I haven't been following this thread since the subject mentioned
IntelliJ, so I'm a little late to the party. While I haven't been doing
anything with cucumber recently, I have used the debugger often in
steps. I have not, though, used the list command, so I can't speak to
the stability of that. Most of what I would do is just check variables
and execute some statements to see what was going on.

It's not much, but hopefully it will help a little.

Peace,
Phillip