On Thu, Feb 3, 2011 at 8:48 AM, Scott Taylor <sc...@railsnewbie.com> wrote:
>
> Probably manually rescuing your debugger call would work:
>
> begin
> debugger
> rescue Exception
> end
>
Thanks, I just tried this but no go, the rspec still trips and fails me out.
Maybe I have a really different methodology but I depend a lot on working
stuff out in the debugger.
>
> Scott
>
> On Feb 3, 2011, at 9:18 AM, David Kahn wrote:
>
> > I am curious as with Test::Unit I could go into the debugger and stay all
> day inside of a test and make all kinds of errors without a problem. With
> rspec I experience that if I make a bad query/ActiveRecord call that it
> flips out and fails the test, throwing me back to the command prompt. This
> is normally not a problem but getting rather annoying right now as I am
> trying to work out some rather complex logic. Any ideas if there is a way to
> bypass this situation?
> >
> > For example:
> >
> > (rdb:1) TuRawBillDetail.includes(:account_subcode).select("DISTINCT
> account_product_id")
> > INTERNAL ERROR!!! missing attribute: account_subcode_id
> >
> > /Users/DK/.rvm/gems/ruby-1.9.2-p136@ncc_billing/gems/activerecord-3.0.3/lib/active_record/association_preload.rb:324:in
> `block in preload_belongs_to_association'
> > ...
> > re/runner.rb:10:in `block in autorun'F.............................
> >
> > Failures:
> > ...
> >
> >
> >
> > David
> > _______________________________________________
> > rspec-users mailing list
> > rspec-users@rubyforge.org
> > http://rubyforge.org/mailman/listinfo/rspec-users
>
> _______________________________________________
> rspec-users mailing list
> rspec-users@rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>
_______________________________________________
rspec-users mailing list
rspec-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/rspec-users
