Re: [Cucumber] [JVM] Debugging in Eclipse

[aslak hellesoy]

On Fri, Jun 8, 2012 at 4:07 PM, Neil Newman <newm...@gmail.com> wrote:
> How do I go about debugging my step definitions? I've tried throwing a
> breakpoint in and running the same maven command under the debug menu but it
> goes right on past my debug point and completes the test. Any suggestions?
>

I use IDEA, not Eclipse, so I can't give you Eclipse tips. There is
nothing Cucumber specific here. The approach would be the same for
plain old JUnit. You have to use remote debugging.

Here is a page that describes how to do it with IDEA (and the now
defunkt cuke4duke, but the approach is the same)

https://github.com/cucumber/cuke4duke/wiki/Debug-Cuke4Duke-Steps

HTH,
Aslak

>
> -- There are two rules:
>
> 1) Please prefix the subject with [Ruby], [JVM] or [JS]. This allows people
> to filter messages.
> 2) Please use interleaved answers
> http://en.wikipedia.org/wiki/Posting_style#Interleaved_style
>
> 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
> https://groups.google.com/d/forum/cukes?hl=en

[Rex Hoffman]

I described a couple of methods here:

https://github.com/cucumber/cucumber-jvm/wiki/IDE-support

I get good behavior from eclipse -- including debugging.

Rex

> cukes+unsubscribe@googlegroups.com. For more options, visit this group at
> https://groups.google.com/d/forum/cukes?hl=en

[Klaus Bayrhammer]

On Friday, June 8, 2012 7:37:50 PM UTC+2, Neil Newman wrote:

I figured it out, it was just a maven problem I resolved with adding forkMode=never to my debug config. Thanks for the prompt responses

A further suggestion: when you use the JUnit-Cucumber Runner the debugging should work out of the box.