On Jul 1, 2010, at 10:48 PM, Woody Peterson
wrote:
What are you experiencing and what are you expecting?
If you use rspec in cucumber, cucumber doesn't support --debug as an
option, so you can't use debuggers in cucumber + rspec.
Given RSpec 2.0's api, the expected behavior is declaring
> What are you experiencing and what are you expecting?
If you use rspec in cucumber, cucumber doesn't support --debug as an
option, so you can't use debuggers in cucumber + rspec.
Given RSpec 2.0's api, the expected behavior is declaring --debug +
debugger drops you into a debugger, and the ex
On Jun 19, 2010, at 5:24 PM, Brian Cardarella wrote:
> On Jun 19, 1:27 pm, Brian Cardarella wrote:
>> I see that I now need to pas -d or --debug with the rspec command line
>> tool to use ruby-debug. What about with Cucumber? RSpec 2.0 Core
>> overwrites Kernel#debugger that ruby-debug uses.
> My
My work-around is to just comment out the debugger method defined in
kernel_extensions.rb in RSpec-core. This doesn't feel like an ideal
solution.
On Jun 19, 1:27 pm, Brian Cardarella wrote:
> I see that I now need to pas -d or --debug with the rspec command line
> tool to use ruby-debug. What a
I see that I now need to pas -d or --debug with the rspec command line
tool to use ruby-debug. What about with Cucumber? RSpec 2.0 Core
overwrites Kernel#debugger that ruby-debug uses.
___
rspec-users mailing list
rspec-users@rubyforge.org
http://rubyforg
