The other options is to do require ‘ruby-debug’ in your development.rb
and test.rb environment files, and just do debugger where you want the
breakpoint in your test
The other options is to do require ‘ruby-debug’ in your development.rb
and test.rb environment files, and just do debugger where you want the
breakpoint in your test
I just have a ‘debug’ snippet in textmate where ‘debug’ => tab
expands to:
So I just insert this into my spec, and then rerun the specs. the
debugger will pop right into the spec, allowing you to step into the
method call, and so on.
The only disadvantage to this approach is that you will need to run
through the rest of the test in the file before hitting the debug line.
$rdebug spec/models/user_spec – s “should error if not new_record”
The – separates the rdebug options from the options for the program
being debugged.
Inspired by this thread, I just submitted a patch which adds a
debugger option (either -u or --debugger like the Rails script/server
script) which includes ruby-debug, and also ensures that the debugger
method is defined if it isn’t already. This allows you to put
debugger invocations in examples and stories and control whether or
not they do anything using the option.