On Jun 24, 2010, at 8:12 AM, Ivo Wever wrote: > Hey, > > Thanks, that works fine and makes sense. Now there are also a few specs > that assert the inverse direction: > > describe SessionsController do > describe "route generation" do > it "should route the destroy sessions action correctly" do > route_for(:controller => 'sessions', :action => 'destroy').should > == "/logout" > end > end > end
route_to delegates to assert_routing, which tests both sides (recognizes and generates). > I understand the route_for method is similarly deprecated; what would be > the idiomatic way to spec that now? > >> Note that the name RSpec::Rails::RoutingSpecMatchers might change in the >> next beta, so this is not a formal API or anything - just a workaround >> for you to get by until the next release. >> > OK, thanks for the warning. As we consciously chose to move to -beta > software, these kinds of things are expected :). _______________________________________________ rspec-users mailing list rspec-users@rubyforge.org http://rubyforge.org/mailman/listinfo/rspec-users
