Databases
StackOverflow2013
Postsdbo
PORouting Error when running controller spec (rspec)
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PORouting Error when running controller spec (rspec)
    primarykey
    data
    text
    <p>I feel like I have everything I need in my routes.rb, my controller, and my controller spec, but for some reason I'm still getting a routing error (ActionController::RoutingError). Here's my controller:</p> <pre><code>class HunchController &lt; ActionController::Base protect_from_forgery def results auth_token_key = params[:auth_token_key] user_id = params[:user_id] @user = User.create! @user.auth_token = @user.get_auth_token(auth_token_key, user_id) @recommended_books = @user.get_recommended_books(@user.auth_token) end end </code></pre> <p>Here's my controller spec:</p> <pre><code>require 'spec_helper' describe HunchController do describe "POST 'results'" do before do @params = { :auth_token_key =&gt; "my auth token", :user_id =&gt; "my user id" } end it "succeeds" do post :results, @params response.should be_success end end end </code></pre> <p>And here's my routes.rb:</p> <pre><code>MyApplicationName::Application.routes.draw do root :to =&gt; 'hunch#index' resources :users post 'hunch/results' =&gt; "hunch#results" match '/results' =&gt; 'hunch#results' end </code></pre> <hr> <p>EDIT: Here's my rake routes output:</p> <pre><code> root / {:controller=&gt;"pages", :action=&gt;"index"} hunch_results POST /hunch/results(.:format) {:controller=&gt;"hunch", :action=&gt;"results"} results /results(.:format) {:controller=&gt;"hunch", :action=&gt;"results"} users GET /users(.:format) {:action=&gt;"index", :controller=&gt;"users"} POST /users(.:format) {:action=&gt;"create", :controller=&gt;"users"} new_user GET /users/new(.:format) {:action=&gt;"new", :controller=&gt;"users"} edit_user GET /users/:id/edit(.:format) {:action=&gt;"edit", :controller=&gt;"users"} user GET /users/:id(.:format) {:action=&gt;"show", :controller=&gt;"users"} PUT /users/:id(.:format) {:action=&gt;"update", :controller=&gt;"users"} </code></pre> <hr> <p>EDIT #2: I'm getting this error with my users#show test too. Here's the actual error:</p> <pre><code> 1) UsersController#show succeeds Failure/Error: get :show ActionController::RoutingError: No route matches {:controller=&gt;"users", :action=&gt;"show"} # ./spec/controllers/users_controller_spec.rb:13:in `block (3 levels) in &lt;top (required)&gt;' </code></pre>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USjyli7
    1. USjyli7
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. PORouting Error when running controller spec (rspec)
      1. USMcGin
      1. VTFavorite
    2. VO
      singulars
      1. PORouting Error when running controller spec (rspec)
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PORouting Error when running controller spec (rspec)
      1. This table or related slice is empty.
      1. VTUpMod
    1. COPlease add your rake routes output.
      singulars
      1. PORouting Error when running controller spec (rspec)
      1. USJohn
    2. COEdited above. Thanks.
      singulars
      1. PORouting Error when running controller spec (rspec)
      1. USjyli7
    3. COWhat's the actual routing error?
      singulars
      1. PORouting Error when running controller spec (rspec)
      1. USAndrew Marshall
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload