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
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 :).
all the best,
--
Ivo
--
Posted via http://www.ruby-forum.com/.
_______________________________________________
rspec-users mailing list
rspec-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/rspec-users
