Rails%203%20In%20Action

Summary
And "user@ticketee.com" has created a ticket for this project:
| title | description |
| Make it shiny! | Gradients! Starbursts! Oh my! |
When you run bin/cucumber features/deleting_tickets.feature, this feature
passes once again:
1 scenario (1 passed)
11 steps (11 passed)
There! The last of the broken features is fixed.
Now that the known failing scenarios are working, let’s check for any other breakages
with rake cucumber:ok spec. You should see this output:
16 scenarios (16 passed)
148 steps (148 passed)
# and
6 examples, 0 failures, 4 pending
Great! Let’s commit and push that to GitHub now:
git add .
git commit -m "When creating tickets, attribute them to the creator."
git push
You’ve added the feature to add attribution to the tickets so that when a ticket is created,
you know who created it. You’ve also restricted certain actions in the Tickets-
Controller on the basis of whether or not a user is signed in.
6.6 Summary
This chapter covered how to set up authentication so that users can sign up and sign
in to your application to accomplish certain tasks.
We began with Devise, a gem that provides the signing up and signing in capabilities
right out of the box by way of being a Rails engine. Using Devise, you tested the
functionality provided by the gem in the same way you tested functionality you wrote
yourself: by writing Cucumber features to go with it.
Then you moved into testing whether emails were sent out to the right people by
using another gem called email_spec. The gem allows you to click a link in an email to
confirm a user’s account and then have Devise automatically sign in the user.
Then came linking tickets to users, so you can track which user created which
ticket. This was done by using the setter method provided by the belongs_to
method’s presence on the Ticket class. You were also able to use Hash’s lovely merge!
method in the TicketsController’s create action to link any ticket that was being
created to the currently signed-in user.
In the next chapter, we look at restricting certain actions to only users who are
signed in or who have a special attribute set on them.
135