Rails%203%20In%20Action

178 CHAPTER 8 More authorization
Removing these scenarios removes two of the failing scenarios, but two more are still
failing:
Failing Scenarios:
cucumber features/hidden_links.feature:21
cucumber features/hidden_links.feature:31
These two scenarios fail because user@ticketee.com doesn’t have access to the Text-
Mate 2 project. To give it access, you can put the permission step underneath the
project-creation step in the Background, like this:
And there is a project called "TextMate 2"
And "user@ticketee.com" can view the "TextMate 2" project
When you run this feature again using bin/cucumber features/hidden_links
.feature, it passes:
7 scenarios (7 passed)
39 steps (39 passed)
You fixed the scenarios in the Hidden Links feature, but the Signing Up feature still
fails. These two features aren’t closely related, so it’s best to make a commit but not
push it to GitHub now so you have all related changes in one commit and other
changes in separate commits. For this commit, the ProjectsController’s index
action is restricted to displaying projects only the user can see, so the commit commands
are as follows:
git add .
git commit -m "Don’t show projects that a
user doesn't have permission to see"
Now let’s see why the Signing Up feature is acting up. When you run it using bin
/cucumber features/signing_up.feature, the final step fails:
Then I should see "You have signed up successfully"
expected #has_content?("You have signed up successfully.")
to return true, got false
When users sign up to your application, they’re shown the “You have signed up successfully”
message, as the feature says they should, and they’re also redirected to the
root of your application. The problem lies with this final step: people are redirected to
the root of the application, the ProjectsController’s index action, which is now
locked down to require that users be authenticated before they can view this action.
This is problematic, but it’s fixable.
8.3.4 Fixing Signing Up
The Signing Up feature is broken, and the problem lies solely with the latest changes
you made to the ProjectsController. When users sign up, they’re sent to the
root_path in the application, which resolves to the index action in the Projects-
Controller. This controller has the authenticate_user! method called before all