Rails%203%20In%20Action

Restricting actions to admins only
key-value pair of the hash, the action 1 and method change. You pass in the :id parameter
because, without it, the controller can’t route to the edit, update, or destroy
action. The new and create actions ignore this parameter.
The remainder of this spec is unchanged, and when you run bin/rspec spec/controllers/projects_controller_spec.rb,
you should see all six examples passing:
6 examples, 0 failures
Now’s a good time to ensure you haven’t broken anything, so let’s run rake cucumber
:ok spec:
cucumber features/deleting_projects.feature:6
cucumber features/editing_projects.feature:12
cucumber features/editing_projects.feature:18
Oops. Three scenarios are broken. They failed because, for these features, you’re not
signing in as an admin user—or, in fact, as any user!—which is now required for performing
the actions in the scenario. You can fix these scenarios by signing in as an
admin user.
7.3.1 Fixing three more broken scenarios
For the features/deleting_projects.feature, add a new Background, as shown in the following
listing.
Listing 7.10 features/deleting_projects.feature
Background:
Given there are the following users:
| email | password | admin |
| admin@ticketee.com | password | true |
And I am signed in as them
When you run this feature, it once again passes:
1 scenario (1 passed)
8 steps (8 passed)
For the editing_projects.feature, use the steps from listing 7.10 again, putting them at
the top of the already existing Background:
Given there are the following users:
| email | password | admin |
| admin@ticketee.com | password | true |
And I am signed in as them
Now this feature also passes. Check it using bin/cucumber features/editing
_projects.feature:
2 scenarios (2 passed)
21 steps (21 passed)
1 The action variable is a frozen string in Ruby 1.9.2 (because it’s a block parameter), so you need to duplicate
the object because Rails forces the encoding on it to be UTF-8.
143