Test the emails your app sends

For anyone whose app sends sign-up, password reset or one-time-code emails. Each run gets its own inbox, so a test can finish the flow without a person checking a mailbox.

How it works

Use the run’s address. Put {{email.address}} in a Fill step. SpinUI swaps in an address that belongs to that run.
Trigger the email. Let your app send the message: submit the sign-up form, or ask for a password reset.
Wait for it. Add a step that waits for the message. Filters on subject or sender are optional, and the step waits for a message that arrived after the run started.
Open it, click or extract. Show the email in the run’s browser, click a link in it by its text or address, or read a one-time code into a variable and type it in a later step.
Check the message. Check the subject, sender, recipient, text and attachments.

What is included

An inbox for each run. It is not a permanent mailbox: it accepts mail during the run and a short time after.
Wait for the message. Add filters on subject or sender if you need them.
Open it or click through. Show the email in the run’s browser, or click a link in it by its text or address.
Extract a code. Read a one-time code from the message into a variable, then type it in a later step.
Check the message. Check the subject, sender, recipient, text and attachments.
See everything that arrived. The run page lists every email received, including ones that did not match a step. Use labels if a test needs more than one inbox.

Plans. Individual and up. Each of those plans has a monthly allowance of received emails.

Good to know

Raw messages are kept for up to 72 hours by default, and an admin can shorten that. Codes are masked in results, but traces and videos show the page as it appeared, including any code on it. Test inboxes are for testing your own applications only.

Questions

Is the test inbox a permanent mailbox?

No. Each run has its own address. It accepts mail during the run and a short time after, and it is not a place to receive real mail.

How long are test emails kept?

Up to 72 hours by default, and an organization admin can shorten that. A summary line with sender, subject and time stays with the run’s history.

Can a test read a one-time code from an email?

Yes. Read the code from the message into a variable, then type it in a later step. Codes are masked in results, but a trace or video shows the page as it appeared.

Which plans include email testing?

Individual and up, each with a monthly allowance of received emails. The pricing page shows the allowance for each plan.

Does an outside email service handle my test emails?

No separate email-testing provider is used. Test emails go to SpinUI’s own mail receiver in our Azure environment in the United States. They are never forwarded anywhere. The sub-processors page has the full list.

Keep reading

Check your site the way a person would

Record your first test by using your site.

Contact us Sign in