Rails%203%20In%20Action

124 CHAPTER 6 Authentication and basic authorization
In this step definition, you use Cucumber’s table format again to specify more than
one user to create. To get to these attributes, iterate through table.hashes, storing
each set of attributes as attributes for each iteration. Inside the iteration, the
create! method creates the user record using these attributes. All of this should look
pretty familiar—you used it to create tickets for a project.
The second step in this scenario is provided by the email_spec gem, and it fails
when you run bin/cucumber features/signing_in.feature again:
And "user@ticketee.com" opens the email with subject "Confirmation
➥instructions"
Could not find email With subject "Confirmation instructions".
Found the following emails:
[]
This is email_spec telling you it can’t find an email with the title “Confirmation
instructions,” which is what Devise would send out if you had told it you wanted users
to be confirmable. You haven’t yet done this, so no emails are being sent.
To make users confirmable, add the :confirmable symbol at the end of the
devise call in app/models/user.rb:
devise :database_authenticatable, :registerable,
:recoverable, :rememberable, :trackable,
:validatable, :confirmable
Now Devise will send confirmation emails when users sign up. When you run bin/
cucumber features/signing_in.feature again, your first step is failing:
Given there are the following users:
| email | password | unconfirmed |
| user@ticketee.com | password | true |
undefined local variable or method 'confirmed_at' for #
The confirmed_at attribute is used by Devise to determine whether or not a user has
confirmed their account. By default, this attribute is nil, indicating the user hasn’t
confirmed yet. The attribute doesn’t exist at the moment, so you get this error.
You could add this attribute to the existing db/migrate/[timestamp]
_devise_create_users.rb migration, but because you already pushed that migration, you
should avoid changing it, as others will have to rerun the migration to get those
changes. Even though it’s just you working on the project at the moment, it’s a good
rule of thumb to not modify migrations that have already been pushed.
Instead, create a new migration to add the confirmed_at field and two others,
confirmation_token and confirmation_sent_at. The confirmation_token is generated
by Devise and used to identify users attempting to confirm their account when
they click the confirmation link from the email. The confirmation_sent_at field is
used also by Devise and tracks the time when the confirmation email was sent:
rails g migration add_confirmable_fields_to_users
Let’s now open this migration and put the code from the following listing inside it.