StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POAdjusting rspec routing tests for nested routes
primarykey
Id
17659900
data
AcceptedAnswerId
0
AnswerCount
1
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-07-15T17:12:32.790
FavoriteCount
0
LastActivityDate
2016-11-08T06:53:15.063
LastEditDate
LastEditorUserId
0
OwnerUserId
1373672
ParentId
0
PostTypeId
1
Score
2
ViewCount
838
LastEditorDisplayName
text
Body
When building my app, I generated scaffolds, which created standard Rspec tests. I'd like to use these tests for coverage, but they seem to be failing due to nested routes: When I run the test, this is its feedback: <pre><code>Failures: 1) ListItemsController routing routes to #index Failure/Error: get("/list_items").should route_to("list_items#index") No route matches "/list_items" # ./spec/routing/list_items_routing_spec.rb:7:in `block (3 levels) in <top (required)>' Finished in 0.25616 seconds 1 example, 1 failure </code></pre> How do I tell Rspec that there are nested routes? Here are the abridged files: list_items_routing_spec.rb: <pre><code>require "spec_helper" describe ListItemsController do describe "routing" do it "routes to #index" do get("/list_items").should route_to("list_items#index") end end </code></pre> list_items_controller_spec.rb: <pre><code>describe ListItemsController do # This should return the minimal set of attributes required to create a valid # ListItem. As you add validations to ListItem, be sure to # adjust the attributes here as well. let(:valid_attributes) { { "list_id" => "1", "project_id" => "1" } } # This should return the minimal set of values that should be in the session # in order to pass any filters (e.g. authentication) defined in # ListItemsController. Be sure to keep this updated too. let(:valid_session) { {} } describe "GET index" do it "assigns all list_items as @list_items" do list_item = ListItem.create! valid_attributes get :index, project_id: 2, {}, valid_session assigns(:list_items).should eq([list_item]) end end </code></pre> routes.rb: <pre><code> resources :projects do member do match "list_items" end end </code></pre> Notes: - I've tried changing the rpec tests themselves to include a project_id, and that didn't help. - I'm using Factory Girl for fixture generation (not sure if this is relevant) Thanks for your help!
Tags
<ruby-on-rails><rspec><routes>
Title
Adjusting rspec routing tests for nested routes
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USQuincy Larson
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
1. This table or related slice is empty.
CommentsPostId
1. This table or related slice is empty.

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.