Steve,
> Giuseppe: have you tried running 'rake routes' to see what the
> application thinks you valid routes are? Reconciling that with what's
> going on in routes.rb is a good next step.
The following line is the whole of the 'rake routes' output:
accept_invitation /accept_invitation/:id
{:action=>"accept", :method=>"get", :controller=>"invitations"}
> Also, when testing behavior has me stumped, I often remember far too
> late to open up my Web browser and poke at the pages directly, as a
> human being.
I did visit:
http://localhost:3000/accept_invitation/1
and the request gets properly routed by the app.
As David pointed out earlier today, this behavior appears to be
related to rails' testing framework, rather than to rspec.
I have raised a ticket in the rails lighthouse:
https://rails.lighthouseapp.com/projects/8994-ruby-on-rails/tickets/3263-failing-functional-test-of-a-named-route
Cheers,
Giuseppe
_______________________________________________
rspec-users mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/rspec-users
