Rails%203%20In%20Action

122 CHAPTER 6 Authentication and basic authorization
14 scenarios (14 passed)
115 steps (115 passed)
# and
6 examples, 0 failures, 5 pending
Great! Commit that!
git add .
git commit -m "Added feature to ensure Devise signup is always working"
git push
In this section, you added a feature to make sure Devise is set up correctly for your
application. When users sign up to your site, they’ll receive an email as long as you
configured your Action Mailer settings correctly. The next section covers how Devise
automatically signs in users who click the confirmation link provided in the email
they’ve been sent.
6.3 Confirmation link sign-in
With users now able to sign up to your site, you should make sure they’re also able to
sign in. When users are created, they should be sent a confirmation email in which
they have to click a link to confirm their email address. You don’t want users signing
up with fake email addresses! Once confirmed, the user is automatically signed in by
Devise.
6.3.1 Testing email
First, you enable the confirmable module for Devise because (as you saw earlier) it’s
one of the optional modules. With this module turned on, users will receive a confirmation
email that contains a link for them to activate their account. You need to write
a test that checks whether users receive a confirmation email when they sign up and
can confirm their account by clicking a link inside that email.
For this test, you use another gem called email_spec. To install this gem, add the
following line to your Gemfile inside the test group:
gem 'email_spec'
Now run bundle to install it.
Next, run the generator to get the steps for email_spec with the following
command:
rails g email_spec:steps
This command generates steps in a file at features/step_definitions/email_steps.rb that
you can use in your features to check whether a user received a specific email and
more. This is precisely what you need to help you craft the next feature: signing in,
receiving an email, and clicking the confirmation link inside it.
One additional piece you must set up is to require the specific files from the
email_spec library. Create a new file at features/support/email.rb, which you use for
requiring the email_spec files. Inside this file, put these lines: