Project

mailosaur

0.04
A long-lived project that still receives updates
The Mailosaur Ruby library lets you integrate email and SMS testing into your continuous integration process.
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
 Dependencies

Development

~> 2.6, >= 2.6.1
~> 12.3, >= 12.3.0
~> 0.68.0
~> 1.2, >= 1.2.2
~> 3.2, >= 3.2.7

Runtime

>= 0.9, < 2
>= 1.7.5, < 4
 Project Readme

Mailosaur - Ruby library ยท

Mailosaur lets you automate email and SMS tests as part of software development and QA.

  • Unlimited test email addresses for all - every account gives users an unlimited number of test email addresses to test with.
  • End-to-end (e2e) email and SMS testing Allowing you to set up end-to-end tests for password reset emails, account verification processes and MFA/one-time passcodes sent via text message.
  • Fake SMTP servers Mailosaur also provides dummy SMTP servers to test with; allowing you to catch email in staging environments - preventing email being sent to customers by mistake.

Get Started

This guide provides several key sections:

  • Get Started
  • Creating an account
  • Test email addresses with Mailosaur
  • Find an email
  • Find an SMS message
  • Testing plain text content
  • Testing HTML content
  • Working with hyperlinks
  • Working with attachments
  • Working with images and web beacons
  • Spam checking

You can find the full Mailosaur documentation on the website.

If you get stuck, just contact us at support@mailosaur.com.

Installation

gem install mailosaur

Then import the library into your code. The value for YOUR_API_KEY is covered in the next step (creating an account):

require 'mailosaur'
mailosaur = Mailosaur::MailosaurClient.new("YOUR_API_KEY")

API Reference

This library is powered by the Mailosaur email & SMS testing API. You can easily check out the API itself by looking at our API reference documentation or via our Postman or Insomnia collections:

Run in Postman Run in Insomnia}

Creating an account

Create a free trial account for Mailosaur via the website.

Once you have this, navigate to the API tab to find the following values:

  • Server ID - Servers act like projects, which group your tests together. You need this ID whenever you interact with a server via the API.
  • Server Domain - Every server has its own domain name. You'll need this to send email to your server.
  • API Key - You can create an API key per server (recommended), or an account-level API key to use across your whole account. Learn more about API keys.

Test email addresses with Mailosaur

Mailosaur gives you an unlimited number of test email addresses - with no setup or coding required!

Here's how it works:

  • When you create an account, you are given a server.
  • Every server has its own Server Domain name (e.g. abc123.mailosaur.net)
  • Any email address that ends with @{YOUR_SERVER_DOMAIN} will work with Mailosaur without any special setup. For example:
    • build-423@abc123.mailosaur.net
    • john.smith@abc123.mailosaur.net
    • rAnDoM63423@abc123.mailosaur.net
  • You can create more servers when you need them. Each one will have its own domain name.

Can't use test email addresses? You can also use SMTP to test email. By connecting your product or website to Mailosaur via SMTP, Mailosaur will catch all email your application sends, regardless of the email address.

Find an email

In automated tests you will want to wait for a new email to arrive. This library makes that easy with the messages.get method. Here's how you use it:

require 'mailosaur'

mailosaur = Mailosaur::MailosaurClient.new("API_KEY")

# See https://mailosaur.com/app/project/api
server_id = "abc123"
server_domain = "abc123.mailosaur.net"

criteria = Mailosaur::Models::SearchCriteria.new()
criteria.sent_to = "anything@" + server_domain

email = mailosaur.messages.get(server_id, criteria)

puts(email.subject) # "Hello world!"

What is this code doing?

  1. Sets up an instance of MailosaurClient with your API key.
  2. Waits for an email to arrive at the server with ID abc123.
  3. Outputs the subject line of the email.

Find an SMS message

Important: Trial accounts do not automatically have SMS access. Please contact our support team to enable a trial of SMS functionality.

If your account has SMS testing enabled, you can reserve phone numbers to test with, then use the Mailosaur API in a very similar way to when testing email:

require 'mailosaur'

mailosaur = Mailosaur::MailosaurClient.new("API_KEY")

server_id = "abc123"

criteria = Mailosaur::Models::SearchCriteria.new()
criteria.sent_to = "4471235554444"

sms = mailosaur.messages.get(server_id, criteria)

puts(sms.text.body)

Testing plain text content

Most emails, and all SMS messages, should have a plain text body. Mailosaur exposes this content via the text.body property on an email or SMS message:

puts(message.text.body) # "Hi Jason, ..."

if message.text.body.include? "Jason"
  puts("Email contains 'Jason'")
end

Extracting verification codes from plain text

You may have an email or SMS message that contains an account verification code, or some other one-time passcode. You can extract content like this using a simple regex.

Here is how to extract a 6-digit numeric code:

puts(message.text.body) # "Your access code is 243546."

match = message.text.body.match(/([0-9]{6})/)
puts(match[0]) # "243546"

Read more

Testing HTML content

Most emails also have an HTML body, as well as the plain text content. You can access HTML content in a very similar way to plain text:

puts(message.html.body) # "<html><head ..."

Working with HTML using nokogiri

If you need to traverse the HTML content of an email. For example, finding an element via a CSS selector, you can use the nokogiri library.

gem install nokogiri
require 'nokogiri'

# ...

@doc = Nokogiri::HTML(message.html.body)
el = @doc.css(".verification-code")

verification_code = el.text

puts verification_code # "542163"

Read more

Working with hyperlinks

When an email is sent with an HTML body, Mailosaur automatically extracts any hyperlinks found within anchor (<a>) and area (<area>) elements and makes these viable via the html.links array.

Each link has a text property, representing the display text of the hyperlink within the body, and an href property containing the target URL:

# How many links?
puts(message.html.links.length) # 2

first_link = message.html.links[0]
puts(first_link.text) # "Google Search"
puts(first_link.href) # "https://www.google.com/"

Important: To ensure you always have valid emails. Mailosaur only extracts links that have been correctly marked up with <a> or <area> tags.

Links in plain text (including SMS messages)

Mailosaur auto-detects links in plain text content too, which is especially useful for SMS testing:

# How many links?
puts(message.text.links.length) # 2

first_link = message.text.links[0]
puts(first_link.href) # "https://www.google.com/"

Working with attachments

If your email includes attachments, you can access these via the attachments property:

# How many attachments?
puts(message.attachments.length) # 2

Each attachment contains metadata on the file name and content type:

first_attachment = message.attachments[0]
puts(first_attachment.file_name) # "contract.pdf"
puts(first_attachment.content_type) # "application/pdf"

The length property returns the size of the attached file (in bytes):

first_attachment = message.attachments[0]
puts(first_attachment.length) # 4028

Working with images and web beacons

The html.images property of a message contains an array of images found within the HTML content of an email. The length of this array corresponds to the number of images found within an email:

# How many images in the email?
puts(message.html.images.length) # 1

Remotely-hosted images

Emails will often contain many images that are hosted elsewhere, such as on your website or product. It is recommended to check that these images are accessible by your recipients.

All images should have an alternative text description, which can be checked using the alt attribute.

image = message.html.images[0]
puts(image.alt) # "Hot air balloon"

Triggering web beacons

A web beacon is a small image that can be used to track whether an email has been opened by a recipient.

Because a web beacon is simply another form of remotely-hosted image, you can use the src attribute to perform an HTTP request to that address:

image = message.html.images[0]
puts(image.src) # "https://example.com/s.png?abc123"

# Make an HTTP call to trigger the web beacon
uri = URI(image.src)
Net::HTTP.start(uri.host, uri.port,
:use_ssl => uri.scheme == 'https') do |http|
request = Net::HTTP::Get.new uri

response = http.request request # Net::HTTPResponse object
puts(response.code) # 200
end

Spam checking

You can perform a SpamAssassin check against an email. The structure returned matches the spam test object:

result = mailosaur.analysis.spam(message.id)

puts(result.score) # 0.5

for r in result.spam_filter_results.spam_assassin do
  puts(r.rule)
  puts(r.description)
  puts(r.score)
end

Development

You must have the following prerequisites installed:

Install all development dependencies:

bundle install

The test suite requires the following environment variables to be set:

export MAILOSAUR_BASE_URL=https://mailosaur.com/
export MAILOSAUR_API_KEY=your_api_key
export MAILOSAUR_SERVER=server_id

Run all tests:

bundle exec rake test

Lint code (via Rubocop):

bundle exec rubocop

Contacting us

You can get us at support@mailosaur.com