If you ever have an error in rspec and the backtrace doesn’t show the line of code that actually threw the error (eg it’s deep inside rails), run rspec with the `—backtrace` flag. That will run the code without backtrace silencers and reveal the true source of the error
@iainbeeston I had to use that recently. I wish there was an option to filter to show only from your code down, ie: showing the framework frames called by your code, as opposed to those calling your code, as normally I’m not interested in the high-level frames, like those from Rack
@iainbeeston @pablobm they are indeed. An alternative approach is to surround the problematic call in the RSpec example with begin/rescue/end block, and manually print out the backtrace, which I do with `pp $!.backtrace`
@iainbeeston Oh: and don't forget to re-raise or you may get a passing example where you shouldn't have one!
@pablobm @iainbeeston you might get close by reconfiguring the backtrace filters to get what you want.
http://rspec.info/features/3-12/rspec-core/configuration/backtrace-exclusion-patterns/
@pablobm yeah it’s a very blunt tool - it also turns regular rspec failures into big backtraces that come up from the intervals of rspec (because I think expectation failures are implemented as errors internally?)