Rails%203%20In%20Action

Confirmation link sign-in
Listing 6.5 db/migrate/[timestamp]_add_confirmable_fields_to_users.rb
class AddConfirmableFieldsToUsers < ActiveRecord::Migration
def change
add_column :users, :confirmation_token, :string
add_column :users, :confirmed_at, :datetime
add_column :users, :confirmation_sent_at, :datetime
end
end
This migration adds the specified columns to the users table when you run rake
db:migrate or removes them when you run rake db:rollback.
When users sign up, a confirmation token is generated for them. An email with a
link containing this token is sent (and the confirmation_sent_at field is set). When
users click the link, their account is confirmed, and the confirmed_at field is set to
the current time in the process.
You now need to run rake db:migrate and rake db:test:prepare to update your
test database with this latest change. With these fields in place, you should be much
closer to having your scenario pass. Let’s see with a quick run of bin/cucumber features/signing_in.feature:
Scenario: Signing in via confirmation
Given there are the following users:
| email | password |
| user@ticketee.com | password |
And "user@ticketee.com" opens the email with subject "Confirmation
➥instructions"
And they click the first link in the email
Then I should see "Your account was successfully confirmed"
Then I should see "Signed in as user@ticketee.com"
expected there to be content "Created by user@ticketee.com" in "[text]"
Everything but the final step is passing. The final step checks for “Signed in as
user@ticketee.com” somewhere on the page, but it can’t find it. You must add it to
your application’s layout, replacing the Sign Up link with “Signed in as [username]”
so users don’t have the option to sign up if they’re already signed in!
Let’s open app/views/layouts/application.html.erb and change this line
to the following:
Signed in as
The user_signed_in? and current_user methods are provided by Devise. The
user_signed_in? method returns true if the user is signed in; otherwise it returns
false. The current_user method returns a User object representing the current
user, and from that object you can call the email method to display the user’s email.
125