Sławosz
Reputation: 11687
How to avoid a long stacktrace in rspec
is it easy way to limit stack trace only to files in application? Long stacktrace is messy and most errors are directly in app.
Upvotes: 11
Views: 1786
Answers (2)
rdaniels
Reputation: 979
I don't think there is currently a way to further reduce the stacktrace, but I'm with you - it would be nice to be able to add something like --backtrace 4 to .rspec that would limit it to 4 lines
Upvotes: 0
nathanvda
Reputation: 50057
Normally the stacktrace is shortened automatically, unless you specify the option --backtrace in .rspec file.
Maybe this question is helpful for you. They try to achieve the opposite, but it shows the point where you can hook in and overrule it.
Upvotes: 8
Related Questions
- RSpec - Check if method was called further down(up?) the call stack
- stack level too deep in rspec
- Is there an idiomatic way to dry up repeated method calls in RSpec
- Rspec Failure/Error: stack level too deep
- Avoid excessive rspec nesting with subject, let, and alternative arguments
- Is it possible to write a spec for infinite-loop issues using Rspec?, Ruby
- rspec stack level too deep
- Is there a way to get a stack trace from rspec when a method is unexpectedly called more times than specified?
- Rspec: Stack level too deep whatever the test
- rspec stack trace on autotest