Rails%203%20In%20Action

Form sign-in
When I follow "Sign in"
no link with title, id or text 'Sign in' found (Capybara::ElementNotFound)
You should add the link directly under the Sign Up link in app/views/layouts
/application.html.erb, as shown in the following listing.
Listing 6.7 app/views/layouts/application.html.erb
When you run the feature again, it still fails, but this time on the final step:
And I press "Sign in"
Then I should see "Signed in successfully."
expected there to be content "Signed in successfully." in "[text]"
It fails because users who have not yet confirmed their account by clicking the link in
the email can’t sign in. To fix this, you could confirm the users with the first step in
this scenario, but it would break the first scenario because it requires users to be
unconfirmed.
To fix this, alter the first scenario in this feature to contain the following as its first
step:
Given there are the following users:
| email | password | unconfirmed |
| user@ticketee.com | password | true |
With this small change, the step now has an additional key available in the attributes
hash in the step definition. If this step is called with an unconfirmed user, it doesn’t
confirm the user; otherwise it does. Let’s alter this step definition in features/
step_definitions/user_steps.rb:
Given /^there are the following users:$/ do |table|
table.hashes.each do |attributes|
unconfirmed = attributes.delete("unconfirmed") == "true"
@user = User.create!(attributes)
@user.confirm! unless unconfirmed
end
end
At the top of the iteration over table.hashes, you now call attributes
.delete("unconfirmed"), which removes the unconfirmed key from the attributes
hash, returning its value in the process. If that value is equal to true then
unconfirmed is also set to true. If that’s the case, the final line in the iterator isn’t
called and the user isn’t confirmed. Otherwise, as in the case in the second scenario of
the feature, the user is confirmed and allowed to sign in.
When you run bin/cucumber features/signing_in.feature again, both scenarios
pass:
2 scenarios (2 passed)
12 steps (12 passed)
127