compared to email-spec? about action_mailer_matchers

[aaackerman]

Hi @daniely, great question! When I was first building ActionMailerMatchers with the folks here at Contently, I took a look at email-spec and felt like the gem was a little heavy for our specific needs.

If you look in the user_mailer_spec.rb example in the repo, it looks like the matchers are being used to unit test the mailer objects specifically. That's great, but the purpose of the have_received_email matcher is to be used in controllers and other services to make sure that emails are being sent when actions are performed. You can see more clearly how action_mailer_matchers could be used by rewriting email-spec's welcome controller test example.

describe "POST /signup (#signup)" do
  it "should deliver the signup email" do
      expect {
        post :signup, "Email" => "[email protected]", "Name" => "Jimmy Bean"
      }.to change(ActionMailer::Base.deliveries, :size).by(1)

      last_delivery = ActionMailer::Base.deliveries.last
      expect(last_delivery.to).to include "[email protected]"
      #message is now multipart, make sure both parts include Jimmy Bean
      expect(last_delivery.parts[0].body.to_s).to include "Jimmy Bean"
      expect(last_delivery.parts[1].body.to_s).to include "Jimmy Bean"
  end
end

With ActionMailerMatchers

describe "POST /signup (#signup)" do
  it "should deliver the signup email" do
    post :signup, "Email" => "[email protected]", "Name" => "Jimmy Bean"
    expect("[email protected]").to have_received_email(body: "Jimmy Bean")
  end
end

If you think an idea from email-spec would be a good addition to this gem, we're happy to hear suggestions or accept pull requests!