Rails%203%20In%20Action

Sending ticket notifications
You’re not really sending emails
These emails aren’t actually sent to these addresses in the real world, but captured
by Action Mailer and stored in ActionMailer::Base.deliveries. You then access
these emails using the helpers provided by email_spec. There’s a setting inside
config/environments/test.rb that goes like this:
config.action_mailer.delivery_method = :test
By default, this setting is set to :smtp, which means that Action Mailer will attempt
to connect to an SMTP server that is running on localhost. You don’t have one of
these set up yet, nor will you. Later on, we’ll look at how you can send real-world
emails from your application using a Gmail account.
The setting in config/environments/test.rb will tell Action Mailer to store all sent
emails internally in ActionMailer::Base.deliveries.
In this feature, you’ll sign in as the second user and create a comment on the ticket
that the first user created. After the comment has been created, the ticket creator
should receive an email and click the View This Ticket Online Here link that will take
them to the updated ticket’s page to see the latest comment. When you run this feature
using bin/cucumber features/ticket_notifications.feature, you see that
everything up to the “should receive an email” step passes, because you’ve already
implemented it all:
Then "alice@ticketee.com" should receive an email
expected: 1,
got: 0 (using ==) ...
When bob@ticketee.com updates the ticket, alice@ticketee.com doesn’t receive an
email, yet. That’s why you wrote the feature: so you can test the behavior that you’re
about to create!
To make alice@ticketee.com receive an email, you’re going to use what’s known as
an observer.
12.1.2 Using observers
An observer is a class that sits outside the model, watching it for specific actions such
as a save to the database. If new instances of the model are created, then the
before_create and after_create methods in the observer will be called. Observers
are handy if you have complex logic for your callbacks, or for sending out email. Hey,
isn’t that what you want to do? Indeed it is!
In this instance, your observer will be called CommentObserver. It’s named like that
because it will observe the Comment model. Observers watch a model for specific
changes and allow you to implement callback-like methods in them to order your
application to do something when an action takes place in the model. Although you
could use a callback in a model, abstracting out code such as this to an observer is
much better because it can lead to reduced code clutter in the model.
315