Ben Mabey wrote:
> Mark,
> Try 'ruby stories/all.rb --backtrace'.
Thanks, that worked.
I think the test actually failed due to a bug in a gem I'm using
(webrat). Without the -backtrace switch RSpec quietens the backtrace by
stopping once it hits a gem it seems. Presumable that's intended?
~ M
Mark Dodwell wrote:
Does anybody know how to get full backtraces for stories when they fail?
I tried 'ruby stories/all.rb --trace' but it doesn't like that option.
Thanks,
~ Mark
Mark,
Try 'ruby stories/all.rb --backtrace'.
I've always had the full stack trace though... What kind of traces
Does anybody know how to get full backtraces for stories when they fail?
I tried 'ruby stories/all.rb --trace' but it doesn't like that option.
Thanks,
~ Mark
--
Posted via http://www.ruby-forum.com/.
___
rspec-users mailing list
rspec-users@rubyforge
Hi Ben,
This is probably not an rspec issue, but a rails defect
( http://dev.rubyonrails.org/ticket/10896 ).
>From your code, I am assuming you are story testing a Rails app. I was
bitten by this too recently... Took me a while to figure it out. The
workaround is to replace
post.id
by
post[:
