bamboo v0.4.2 Bamboo.Test
Helpers for testing email delivery
Use these helpers with Bamboo.TestAdapter to test email delivery. Typically you’ll want to unit test emails first. Then in integration tests use helpers from this module to test whether that email was delivered.
Note on sending from other processes
If you are sending emails from another process (for example, from inside a
Task or GenServer) you may need to use the process_name option when using
Bamboo.Test. See the docs __using__/1 for an example.
For most scenarios you will not need the process_name option.
In your config
# Typically in config/test.exs
config :my_app, MyApp.Mailer,
adapter: Bamboo.TestAdapter
Unit test
You don’t need any special functions to unit test emails.
defmodule MyApp.EmailsTest do
use ExUnit.Case
test "welcome email" do
user = %User{name: "John", email: "person@example.com"}
email = MyApp.Email.welcome_email(user)
assert email.to == user
assert email.subject == "This is your welcome email"
assert email.html_body =~ "Welcome to the app"
end
end
Integration test
defmodule MyApp.Email do
import Bamboo.Email
def welcome_email(user) do
new_email(
from: "me@app.com",
to: user,
subject: "Welcome!",
text_body: "Welcome to the app",
html_body: "<strong>Welcome to the app</strong>"
)
end
end
defmodule MyApp.EmailDeliveryTest do
use ExUnit.Case
use Bamboo.Test
test "sends welcome email" do
user = %User{...}
email = MyApp.Email.welcome_email(user)
email |> MyApp.Mailer.deliver_now
# Works with deliver_now and deliver_later
assert_delivered_email MyAppEmail.welcome_email(user)
end
end
Summary
Functions
Checks whether an email was delivered
Checks that no emails were sent
Ensures a particular email was not sent
Macros
Imports Bamboo.Test and Bamboo.Formatter.format_email_address/2
Functions
Checks whether an email was delivered.
Must be used with the Bamboo.TestAdapter or this will never pass. If a Bamboo.Email struct is passed in, it will check that all fields are matching.
You can also pass a keyword list and it will check just the fields you pass in.
Examples
email = Bamboo.Email.new_email(subject: "something")
email |> MyApp.Mailer.deliver
assert_delivered_email(email) # Will pass
unsent_email = Bamboo.Email.new_email(subject: "something else")
assert_delivered_email(unsent_email) # Will fail
Checks that no emails were sent.
Under the hood this uses ExUnit.Assertions.refute_received, so if you are
delivering emails from another process (for example, within Task.async) you
may have a race condition where this assertion is called before the email was
received by the test process, resulting in an incorrect test.
Ensures a particular email was not sent
Same as assert_delivered_email, except it checks that an email was not sent.
Under the hood this uses ExUnit.Assertions.refute_received, so if you are
delivering emails from another process (for example, within Task.async) you
may have a race condition where this assertion is called before the email was
received by the test process, resulting in an incorrect test.
Macros
Imports Bamboo.Test and Bamboo.Formatter.format_email_address/2
Bamboo.Test and the Bamboo.TestAdapter work by sending a message to the
current process when an email is delivered. The process mailbox is then
checked when using the assertion helpers like assert_delivered_email/1.
Sometimes emails don’t show up when asserting because you may deliver an email
from a different process than the test process. When that happens, set the
process_name. This will name the test process using Process.register/2
and set Bamboo.TestAdapter to always send to that process. This means
that you cannot use process_name with async tests.
Try to use this version first
use Bamboo.Test
And if you are delivering from another process, set process_name
# Note: the process name can be whatever you want.
use Bamboo.Test, process_name: :name_of_my_test
Common scenarios for delivering mail from a different process are when you send from inside of a Task, GenServer, or are running acceptance tests with a headless browser like phantomjs.