search for: bypass_rescue

As best I can tell, bypass_rescue from rspec-rails-1 is no longer part of rspec-rails, ''> 2''. I had been using it on occasion for things like: describe CorrespondencesController do ... describe ''#show'' do it "should raise an AuthorizationError if current user is not the corresponde...

Hey, I''ve just started using rspec-rails 1.2 and the bypass rescue declaration is wonderful - by default I tend to write controller which raise exceptions (in exceptional circumstances), along with before- filters as guard clauses, so being able to switch off rescue from (which I properly spec separately) is a real boon. Such a boon, in fact, that I immediately shoved it into a

...y/Gems/1.8/gems/actionpack-2.2.2/lib/action_controller/assertions.rb:54:in `clean_backtrace'' /Library/Ruby/Gems/1.8/gems/actionpack-2.2.2/lib/action_controller/assertions/routing_assertions.rb:47:in `assert_recognizes'' ./spec/controllers/thoughts_routing_spec.rb:9: I tried using bypass_rescue in my routing/items_routing_spec.rb file as mentioned by the upgrade doc, but it wasn''t valid in the "routing" spec - worked fine when I moved the file back to spec/controllers/, though. Seems like that''s not the issue, but I''m mentioning for more completeness....

...emplate is implicit subject in view specs (Joe Ferris). #686. * redirect_to and render_template matchers can accept controller or response (Joe Ferris). Closes #686. * generated specs use declarative docstrings * rspec_scaffold generator generates layout and stylesheet (per Rails-2.3) * add bypass_rescue for controller specs * infer template path from the first arg passed to describe in view specs * separate routing specs (in spec/routing) * bug fixes * you no longer *have* to load ActionMailer to get specs to run. Closes #650. * query_params are now parsed by Rack::Utils.parse_query in r...