This project is archived and is in readonly mode.
multiple nested routes for same resource doesn't work in functional tests?
#4446
Say I have routes like so:
ActionController::Routing::Routes.draw do |map|
map.resources :tabs do |tab|
tab.resources :contacts, :collection => {
:bar => :get
}
end
map.resources :clients do |client|
client.resources :contacts, :collection => {
:foo => :get
}
end
map.root :controller => 'clients', :action => 'root'
end
These routes will work as expected via the webserver, but they will fail in functional tests. Example app attached.
-
routing_error.zip
104 KB
-
jemminger- Tag set to routing error, functional, routingerror, testing
-
jemminger
- Title changed from multiple nested routes for same route doesn't work in functional tests? to multiple nested routes for same resource doesn't work in functional tests?
-
gnufied
Your functional test has code like:
class ContactsControllerTest < ActionController::TestCase test 'should get foo' do get :foo assert_response :success end test 'should get bar' do get :bar assert_response :success end endbut in your routes.rb, you have marked contacts as nested resource and hence isn't accessible directly. In short, accessing contacts resource directly doesn't work from browser, doesn't work from functional tests. There ain't anything wrong with behavior.
-
gnufied
- Tag changed from routing error, functional, routingerror, testing to routing error, functional, invalid, routingerror, testing
-
jemminger
Doh, you're right. Changing the tests like so fixes it:
test 'should get foo' do get :foo, :client_id => 1 assert_response :success end test 'should get bar' do get :bar, :tab_id => 1 assert_response :success endAnd this is how I've set up all my other tests, but for whatever reason brainfarted here and forgot.
-
-
Ryan Bigg- State changed from new to invalid