Rails%203%20In%20Action

6.2 User signup
User signup
With Devise set up, you’re ready to write a feature that allows users to sign up. The
Devise gem provides this functionality, so this feature will act as a safeguard to ensure
that if the functionality were ever changed, the feature would break.
To make sure this functionality is always available, you write a feature for it, using
the following listing, and put it in a new file at features/signing_up.feature.
Listing 6.2 features/signing_up.feature
Feature: Signing up
In order to be attributed for my work
As a user
I want to be able to sign up
Scenario: Signing up
Given I am on the homepage
When I follow "Sign up"
And I fill in "Email" with "user@ticketee.com"
And I fill in "Password" with "password"
And I fill in "Password confirmation" with "password"
And I press "Sign up"
Then I should see "You have signed up successfully."
When you run this feature using bin/cucumber features/signing_up.feature,
you’re told it can’t find a Sign Up link, probably because you haven’t added it yet:
no link with title, id or text 'Sign up' found
You should now add this link in a nav: 1
You previously used the menu on the app/views/tickets/show.html.erb page to style the
links there. Here you use a nav tag because this is a major navigation menu for the
entire application, not just a single page’s navigation.
With this link now in place, the entire feature passes when you run it because
Devise does all the heavy lifting for you:
1 scenario (1 passed)
7 steps (7 passed)
Because Devise has already implemented this functionality, you don’t need to write
any code for it. This functionality could be overridden in your application, and this
feature is insurance against anything changing for the worse.
With the signup feature implemented, this is a great point to see if everything else
is working by running rake cucumber:ok spec. You should see this output:
1 nav is an HTML5 tag and may not be supported by some browsers. As an alternative, you could put instead, in app/views/layouts/application.html.erb, directly underneath the h1 tag for your
application’s title.
121