Rails%203%20In%20Action

126 CHAPTER 6 Authentication and basic authorization
When you run bin/cucumber features/signing_up.feature, the entire feature is
passing:
1 scenario (1 passed)
5 steps (5 passed)
In addition to signing-up facilities, Devise handles all the signing-in facilities too. All
you need to add is the :confirmable symbol to the devise call in the model, the confirmation
fields to the users table, and the message “Signed in as [user]” in your
application—three easy steps.
Does everything else pass? Run rake cucumber:ok spec, and you should see the
following output:
15 scenarios (15 passed)
120 steps (120 passed)
# and
6 examples, 0 failures, 5 pending
Great! Push that!
git add .
git commit -m "Added feature for ensuring that a user is signed in
via a confirmation email by using email spec"
git push
Now that users can sign up and confirm their email addresses, what should happen
when they return to the site? They should be able to sign in! Let’s make sure this can
happen.
6.4 Form sign-in
The previous story covered the automatic sign-in that happens when users follow the
confirmation link from the email they receive when they sign up. Now you must write
a story for users who have confirmed their account and are returning and need to sign
in again.
Place the scenario in the following listing directly underneath the previous scenario
in features/signing_in.feature.
Listing 6.6 features/signing_in.feature
Scenario: Signing in via form
Given there are the following users:
| email | password |
| user@ticketee.com | password |
And I am on the homepage
When I follow "Sign in"
And I fill in "Email" with "user@ticketee.com"
And I fill in "Password" with "password"
And I press "Sign in"
Then I should see "Signed in successfully."
When you run bin/cucumber features/signing_in.feature, it complains about the
missing Sign In link: