On Sat, Sep 26, 2009 at 11:49 AM, giuseb <[email protected]> wrote: >> The bad news is that this is a deficiency the underlying Rails testing >> framework that rspec-rails wraps. I tried the same example in a rails >> functional test and got the same failure: >> >> class InvitationsControllerTest < ActionController::TestCase >> >> test "the post accept invitation should be successful" do >> get :accept, :id => "1" >> assert_response :success >> end >> end >> >> test_the_post_accept_invitation_should_be_successful(InvitationsControllerTest): >> ActionController::RoutingError: No route matches {:action=>"accept", >> :controller=>"invitations", :id=>"1"} >> /test/functional/invitations_controller_test.rb:6:in >> `test_the_post_accept_invitation_should_be_successful' >> >> You wanna raise a ticket in the rails lighthouse? > > I just did--my very first ticket!! > > Two more things: > - I noticed that you tested a get request, while i was doing post.
Oh yeah - I had tried both and copied the wrong one in the email :) > Tried them both again, same outcome. > - what did your "unclean" routes look like that did NOT cause the > problem? Just the defaults: map.connect ':controller/:action/:id' HTH > > Thanks, > Giuseppe > _______________________________________________ > rspec-users mailing list > [email protected] > http://rubyforge.org/mailman/listinfo/rspec-users > _______________________________________________ rspec-users mailing list [email protected] http://rubyforge.org/mailman/listinfo/rspec-users
