I had this happen before and I think the --format pretty option made it show 
the error. It's been a while, so it may be just all muddled up in the maelstrom.

-- 
Ryan Bigg

On Wednesday, 16 February 2011 at 3:41 PM, Jason Nah wrote: 
> -b didn't do a thing for me in this case. The error didn't produce any 
> backtraces at all.
> 
> Using the debugger was the only way to go.
> 
> On 16 February 2011 14:37, Chris Herring <[email protected]> 
> wrote:
> > You can pass -b I believe to Cucumber and it will throw a backtrace on 
> > failure.
> > On Wednesday, 16 February 2011 at 9:43 AM, Jason Nah wrote: 
> > > I've found the root cause of my problem.
> > > 
> > > Thanks Gregory for the tip. I went with that approach to diagnose the 
> > > problem. I stuck a breakpoint in a Before do end statement and then did 
> > > the following:
> > > cat StandardError (to breakpoint when a cucumber error was thrown) 
> > > cont
> > > 
> > > Turns out, that in env.rb I was requiring 'cucumber/rails/active_record' 
> > > which indirectly has a runtime dependency on DatabaseCleaner which I had 
> > > not included as a dependency in my Gemfile.
> > > 
> > >  The failure occurred BEFORE the feature ran, hence the failure at the 
> > > start and end, and all the steps were skipped.
> > > 
> > > I guess the annoying thing was that the error wasn't reported properly 
> > > (no backtrace), and the dependency is a runtime dependency not a 
> > > load-time dependency, causing the error to surface as the feature ran, 
> > > rather than when cucumber loaded.
> > > 
> > > 
> > > Cheers,
> > > Jason
> > > 
> > > 
> > > On 16 February 2011 06:44, Gregory McIntyre <[email protected]> wrote:
> > > >  Also, tried with --format pretty and maybe --expand ?
> > > > 
> > > >  --
> > > > Gregory McIntyre
> > > > 
> > > >  --
> > > >  You received this message because you are subscribed to the Google 
> > > > Groups "Ruby or Rails Oceania" group.
> > > >  To post to this group, send email to [email protected].
> > > >  To unsubscribe from this group, send email to 
> > > > [email protected].
> > > >  For more options, visit this group at 
> > > > http://groups.google.com/group/rails-oceania?hl=en.
> > > > 
> > > > 
> > >  -- 
> > >  You received this message because you are subscribed to the Google 
> > > Groups "Ruby or Rails Oceania" group.
> > >  To post to this group, send email to [email protected].
> > >  To unsubscribe from this group, send email to 
> > > [email protected].
> > >  For more options, visit this group at 
> > > http://groups.google.com/group/rails-oceania?hl=en.
> > > 
> >  -- 
> >  You received this message because you are subscribed to the Google Groups 
> > "Ruby or Rails Oceania" group.
> >  To post to this group, send email to [email protected].
> >  To unsubscribe from this group, send email to 
> > [email protected].
> >  For more options, visit this group at 
> > http://groups.google.com/group/rails-oceania?hl=en.
> > 
>  -- 
>  You received this message because you are subscribed to the Google Groups 
> "Ruby or Rails Oceania" group.
>  To post to this group, send email to [email protected].
>  To unsubscribe from this group, send email to 
> [email protected].
>  For more options, visit this group at 
> http://groups.google.com/group/rails-oceania?hl=en.
> 

-- 
You received this message because you are subscribed to the Google Groups "Ruby 
or Rails Oceania" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/rails-oceania?hl=en.

Reply via email to