Rails%203%20In%20Action

Sending ticket notifications
The template is the final part for your feature: yay! When you run bin/cucumber
features/ticket_notifications.feature, you see that it’s now all passing:
1 scenario (1 passed)
18 steps (18 passed)
When the email is opened for this final time, you see that it has the content you’re
looking for:
Hello!
bob@ticketee.com has just updated the Release date ticket for TextMate 2.
➥They wrote:
Is it out yet?
You can view this ticket online by going to:
➥http://localhost:3000/projects/1/tickets/1
You’ve done quite a lot to get this little simple feature to pass.
In the beginning you created an observer called CommentObserver, which watches
the Comment model for any specific changes. You defined an after_create method on
this, which took the comment object that was being updated and then called Notifier
.comment_updated, passing along the comment object.
Notifier is an Action Mailer class that is responsible for sending out emails to the
users of your application, and in this file you defined the comment_updated method
called in your CommentObserver and set the recipients up to use the comment
object’s related ticket watchers.
To define the watchers method, you used a has_and_belongs_to_many join table
again. Your first experience using these was back in chapter 10, when you linked the
Ticket and Tag models by setting one up on both of them. Back then, you used the
tags_tickets table to link the two. This is the default naming schema of a has_and
_belongs_to_many join table in Rails. In the case of your ticket watchers, however,
your method was called watchers, and so would look for a class called Watcher to
determine where it should find your watchers. This was incorrect, so you told your
association that your join table should be ticket_watchers and that the related
model was User, not Watcher. You used the :join_table and :class_name methods
for this.
Finally, you defined the template for the comment_updated email at app/views/
notifier/comment_updated.html.erb and filled it with the content you’re expecting to
see, including the link that you click to complete the final step of your scenario.
This scenario completes the first steps of sending email notifications to your users.
You should now run all your tests to make sure you didn’t break anything by running
rake cucumber:ok spec:
60 scenarios (60 passed)
676 steps (676 passed)
# and
40 examples, 0 failures, 19 pending
321