Scott Taylor wrote:
Go and file a bug report then, but if you only give this level of
detail, the bug will never get fixed.
I am not reporting any bug in RSpec. Read the Subject line.
I think I know why RSpec has an option (-b) to turn off incomplete stack traces.
The various Ruby editors have feeble support for Fault Navigation. At fault
time, I would like keystrokes that move, optionally, to each line that threw an
error, or each line in project code on the stack trace above an error, or even
each line in library code above an error.
So RSpec, assuming its editor cannot support that simple feature, simply picks
the short trace, to emphasize its own .should lines that faulted.
(Many's the time we have squinted at a humongoid stack trace from Rails, trying
to see the difference between all the library code and our own lines!)
--
Phlip
http://www.oreillynet.com/onlamp/blog/2008/05/dynamic_languages_vs_editors.html
_______________________________________________
rspec-users mailing list
rspec-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/rspec-users
