Rails%203%20In%20Action

144 CHAPTER 7 Basic access control
That should be the last of it. When you run rake cucumber:ok, everything once again
passes:
16 scenarios (16 passed)
158 steps (158 passed)
Great! Now that accessing the actions is restricted, let’s make a commit here:
git add .
git commit -m "Restrict access to project
actions to admins only"
git push
You should also hide the links from the users who are not admins, because it’s useless
to show actions to people who can’t perform them.
7.3.2 Hiding the New Project link
Next you’ll learn how to hide certain links, such as the New Project link, from users
who have no authorization to perform that action in your application. To begin,
write a new feature called features/hidden_links.feature, which looks like the following
listing.
Listing 7.11 features/hidden_links.feature
Feature: Hidden Links
In order to clean up the user experience
As the system
I want to hide links from users who can't act on them
Background:
Given there are the following users:
| email | password | admin |
| user@ticketee.com | password | false |
| admin@ticketee.com | password | true |
And there is a project called "TextMate 2"
Scenario: New project link is hidden for non-signed-in users
Given I am on the homepage
Then I should not see the "New Project" link
Scenario: New project link is hidden for signed-in users
Given I am signed in as "user@ticketee.com"
Then I should not see the "New Project" link
Scenario: New project link is shown to admins
Given I am signed in as "admin@ticketee.com"
Then I should see the "New Project" link
When you run this feature using bin/cucumber features/hidden_links.feature,
you’re given three new steps to define:
Then /^I should not see the "([^\"]*)" link$/ do |arg1|
pending # express the regexp above with the code you wish you had
end