ActionController::RoutingError: No route matches [...]

[Shahor]

I'm writting an API for a pet project of mine and was running rails 3.2.9
I decided to update rails in order to avoid security problems but I suddenly ran into some problems.

I've been able to resolve most of them but I keep getting this and don't know what to do with it.

I am using RSPEC to test a json API and until this upgrade everything was going just fine and all routes were working perfectly.

I'm not sure wether it's a bug or a bad usage from me, so I'm sorry if it's the former.
Here is my code :

Routes :

Fake::Application.routes.draw do
    namespace :api do
        namespace :v1 do
            scope '/user' do
                match "signup" => "registrations#create", :via => :post
                match "delete" => "registrations#destroy", :via => :delete

                match "login"  => "sessions#create", :via => :post
                match "logout" => "sessions#destroy", :via => :delete
            end
        end
    end
end

Spec :

require 'spec_helper'

describe Api::V1::SessionsController do
    before do
        @user = {
            :email => Faker::Internet::email,
            :pseudo => Faker::Internet::user_name,
            :password => Faker::Lorem::words(2).join
        }
        user = User.create @user
    end

    context 'should login in' do

        it 'should be ok ' do
            post '/api/v1/user/login', :user => @user
            JSON.parse(response.body)["success"].should == true
        end

        it 'should fail without credentials' do
            post '/api/v1/user/login', {}
            JSON.parse(response.body)["success"].should == false
        end
    end
end

And the result :

± rspec spec/controllers/sessions_controller_spec.rb                                                                                                                    5:21:10 PM
Rack::File headers parameter replaces cache_control after Rack 1.5.
FF

Failures:

  1) Api::V1::SessionsController should login in should be ok with auth_token
     Failure/Error: post '/api/v1/user/login', :user => @user
     ActionController::RoutingError:
       No route matches {:user=>{:email=>"meghan.breitenberg@bodehansen.org", :pseudo=>"linwood_gislason", :password=>"repellendusaliquid"}, :controller=>"api/v1/sessions", :action=>"/api/v1/user/login"}
     # ./spec/controllers/sessions_controller_spec.rb:17:in `block (3 levels) in <top (required)>'

  2) Api::V1::SessionsController should login in should fail without credentials
     Failure/Error: post '/api/v1/user/login', {}
     ActionController::RoutingError:
       No route matches {:controller=>"api/v1/sessions", :action=>"/api/v1/user/login"}
     # ./spec/controllers/sessions_controller_spec.rb:22:in `block (3 levels) in <top (required)>'

Finished in 0.50905 seconds
2 examples, 2 failures

Failed examples:

rspec ./spec/controllers/sessions_controller_spec.rb:15 # Api::V1::SessionsController should login in should be ok with auth_token
rspec ./spec/controllers/sessions_controller_spec.rb:21 # Api::V1::SessionsController should login in should fail without credentials

Edit :

Rails version : 3.2.11
Rspec version : 2.12.2
Ruby version : ruby 1.9.3p0

[alindeman]

Did you also upgrade rspec or rspec-rails? If so, from what version to what version (rspec-rails only just released 2.12.2)?

[Shahor]

I did a global update of my gems on my system and updated the Gemfile.lock with "bundle update".

It is using rspec-rails 2.12.2 and rspec 2.12.2

below is an excerpt of my Gemfile.lock

 rspec-core (2.12.2)
    rspec-expectations (2.12.1)
      diff-lcs (~> 1.1.3)
    rspec-mocks (2.12.1)
    rspec-rails (2.12.2)
      actionpack (>= 3.0)
      activesupport (>= 3.0)
      railties (>= 3.0)
      rspec-core (~> 2.12.0)
      rspec-expectations (~> 2.12.0)
      rspec-mocks (~> 2.12.0)

I find it weird that rspec-mocks is not 2.12.2 but 2.12.1 but well...

[dchelimsky]

I find it weird that rspec-mocks is not 2.12.2 but 2.12.1 but well...

That is quite intentional. We don't want to have to release the whole suite to do patch releases on each gem, so the rspec gem depends on "rspec-xxx", "~> 2.12.0" where xxx is replaced by each of "core", "expectations", and "mocks": https://github.com/rspec/rspec/blob/master/rspec.gemspec#L31

In this case, 2.12.1 is the latest 2.12 release of rspec-core and rspec-mocks, whereas 2.12.2 is the latest release of rspec-expectations. Make sense?

[dchelimsky]

BTW you can see that expressed in the last 3 lines of the part of Gemfile.lock you posted above:

rspec-core (~> 2.12.0)
rspec-expectations (~> 2.12.0)
rspec-mocks (~> 2.12.0)

[Shahor]

Makes sense :)
Thanks

[rafael]

@Shahor were you able to find a workaround for this issue? I'm having the exact same problem.

[Shahor]

@rafael It's a spare project and I didn't have much time this week so I didn't really dig.
Plus I'm "fairly new" to testing so I really don't know where to check for a solution =/

I don't know how to resolve this. If you have any idea feel free to comment again :)

[Shahor]

I'm upping this since I have no idea what to do on the matter :(

Anyone has an idea/suggestion about how to make this work ? I don't know where to start looking at.

[kmcphillips]

I am experiencing the same issue. I upgraded Rails version, along with rspec and rspec-rails. Now most of my controller tests fail with ActionController::RoutingError.

The application continues to work as expected though.

[Shahor]

Yup, I would happily fix this if I knew where to start from :)

[kmcphillips]

Well. My problem turned out to be with nested controllers and the change between journey 1.0.3 and 1.0.4.

The following works through the app, but would raise ActionController::RoutingError in a test:

resources :payments, only: [:index] do
  resources :payment_policies, only: [:index], controller: "Payments::PaymentPolicies"
end

But replacing it with:

resources :payments, only: [:index] do
  resources :payment_policies, only: [:index], controller: "payments/payment_policies"
end

Or:

resources :payments, only: [:index] do
  resources :payment_policies, only: [:index], module: :payments
end

Fixes the problem. I'm not entirely sure where I should report a bug. Perhaps the controller syntax I was using is deprecated. But it may have broken. @alindeman have any input?

[kmcphillips]

FYI that code is copied out of a proof of concept rails app available here:

https://github.com/kmcphillips/rspec_rails_routing_error_example

I don't really know if this is a bug I should report somewhere, or if that routing syntax was just working incidentally.

[Shahor]

I tend to think it's a bug since my router doesn't really look like yours and is still not working =/
I can't find a way to rewrite it to make it work actually.

MyApp::Application.routes.draw do
    namespace :api do
        namespace :v1 do
            # user stuff
            scope '/user' do
                match "signup" => "registrations#create", :via => :post
                match "delete" => "registrations#destroy", :via => :delete

                match "login"  => "sessions#create", :via => :post
                match "logout" => "sessions#destroy", :via => :delete
            end
        end
    end
end

(thanks for the update 👍 )

[Awea]

You're spec is in the context of Api::V1::SessionsController so you just have to call the correct action :

context 'should login in' do

        it 'should be ok ' do
            post :create, {}
            JSON.parse(response.body)["success"].should == true
        end

        it 'should fail without credentials' do
            post :create, {}
            JSON.parse(response.body)["success"].should == false
        end
end

For me it works.