mailtrap-sticker-11

Remove QA headache while testing email delivery

| 2 Comments

Are you a QA engineer or tester? Have you ever sent emails to real users by mistake? Did you have to create additional email accounts for testing and was it difficult to trace emails from a bunch of mailboxes? If your answer is “Yes” for at least one question, this article would be useful for you.

I am a QA engineer who works on different projects and all of them are web-applications which have at least one feature connected to email delivery. For instance, “SignUp” feature, though, surely, there are more and more of them. Users should get email notifications not only in case of password reminder or email verification, they also get tons of emails about their activity on application, additional information about new possibilities and functionality, or any other actual, urgent and new information.

While testing different type of emails, I might do a lot of boring tasks:

  • create huge amounts of real unique emails for new users registration
  • check letters with different content to different users with different roles
  • be attentive while checking emails on some mail services which group letters with similar subject name
    make a lot of extra mouse clicks

It also happened that during new feature development and its testing, some letters accidentally had been sent to real users. On some projects, developers setup users database by cloning it from production with all information: their personal, contact data and emails. It happened to me once while testing a new feature that I sent for about 100 letters to real users. It wasn’t so critical and they didn’t suffer much, but still it happened. And I know a case when more than 100000 emails were delivered to real users by mistake! Not good, right?

So we came with an idea of creating a simple but effective application which will help to easily test email distribution, not affecting real customers and which may be also useful not only for Railsware engineers but to other QA and developers all over the world.

And we did it!

Here is “Mailtrap”

What is Mailtrap?

Mailtrap is a simple and easy to use application designed and developed by Railsware. It is aimed to test email delivery functionality and catch all emails sent from staging server and not harm real users. It is easy to setup and user friendly.

What are the benefits of using Mailtrap?
  1. First one and the most important benefit is that I have an ability to collect all sent emails from different projects in one Mailtrap account and view them online easily.

    List of inboxes. Ruby on Rails application

    After I started using Mailtrap, the only need which drives me to a real inboxes and services (like Google, Yahoo, and so on) is to check whether layout is still ok and not broken. For that, I just forward my email manually to a proper account. In other cases, I just use Mailtrap.

  2. The second and also a huge benefit is that I stopped creating bunch of new accounts and use a real one for testing. I can enter any valid-email-looking address and I’ll get a message sent on it. So, I shouldn’t create additional mailboxes anymore!
  3. If I want to share any received email with my team members, it’s not necessary to
    forward it, I can just copy URL and send it. It could also be used while bug posting for the reference, as the URL is static.
  4. In Mailtrap, I have an ability to forward email to certain addresses.
    Such cases like:

    - there are some exceptions or errors on stage server and all
    emails are caught by Mailtrap
    - developers don’t use Mailtrap every minute
    - they are more attentive to their real mailboxes

    So, I just have to put email addresses of recipients in a text area, and they will get all notifications.

    Account settings. RoR development.

  5. Mailtrap is also a good solution for layout testing. While using it, I have an ability to check emails with html, txt, message source code view, CSS reseting.
    Rails Developer tools. QA
  6. Each Mailtrap user can share his inboxes with team members or give access to them to any user of certain domain group. It is very simple, just put email of a team member or domain name to the proper field and click Add.
  7. Mailtrap is easy to set up and is adapted to different programming languages.
    List of languages. Ruby development

    After registration, you get Mailtrap’s SMTP settings and credentials, which you should place to your application configuration (non-production environment). And that’s all, all emails will be trapped but still available for you to operate with.

  8. Mailtrap keeps all your email history and attachments.

    List of emails. RoR development

  9. And it’s totally FREE for everybody. Yay! ))

It’s easy, useful, and indispensable in testing.

Use and Enjoy!

You can also check video with Mailtrap presentation from Railsberry Lightning talks by Yaroslav Lazor here.

Share
* Railsware is a premium software development consulting company, focused on delivering great web and mobile applications. Learn more about us.
  • Guest

    AMAZING

  • http://twitter.com/SimplyH Ha Vo

    Hi Anna, I just know that every development team needs a service like Mailtrap. The question is how to get people to spread the word about it. Would it be possible to build in a ‘Tweet a quote’ interface for every time a user uses the system? Of course you can think about gamifying it … Let’s say that 500 users use mailtrap per month, how to get 10% of them to post it into their twitter feed of facebook timeline?

Want to get more of Railsware blog?

RSS FEED

We're always ready to help!

CONTACT US