How to avoid a long stacktrace in rspec

Question

Is it easy to limit the stack trace to only files in the application? A long stacktrace is useless, and most errors are directly in the application.

Answer 1

Typically, stacktrace is automatically reduced if you do not specify the --backtrace option in the --backtrace file.

Maybe this question is useful for you. They try to achieve the opposite, but it shows where you can hook and undo it.

Answer 2

I don't think there is currently a way to further reduce stacktrace, but I am with you - it would be nice to add something like --backtrace 4 to .rspec, which would limit it to 4 lines