Skip to main content

Creating an email inbox

Spur provides SpurMail, a built-in email inbox service, for email testing. To get started, you can create an inbox in one of two ways:
  • Type @ in the beginning of a step
  • Use the / menu and select Email
You can either:
  • Automatically generate a Quick Inbox (random email per test run)
  • Define a Custom Inbox (persistent, named inbox)
Email inbox options in the step editor

Quick inbox

Generates a new random email address for each test run. Use case: Great for testing flows that require a fresh email for every sign-up.
Quick Inbox option generating a random email address

Custom inbox

Specify a named inbox you can reference across test steps. Use case: Adds consistency and specificity in the email address.
Custom Inbox option with a named inbox
Custom Inbox name field in the step editor

Use a scenario value as the inbox username

First, connect a Scenario Table to the containing Test Suite. In the Custom Inbox username field, type [ and select a Scenario Table column. Spur inserts a chip and uses the value from each scenario row. You can combine the chip with a fixed username prefix.

Available actions

Once you create an inbox, several actions are available to you:
  • Open Inbox – opens the inbox in a new tab
  • Read Latest Email – jumps directly to the most recent message
  • Close Inbox – closes the inbox tab and continues the test
  • Close and Clear Inbox – clears inbox contents and resets for the next run
  • Send Email – sends an email to a specified address with a subject and body
Available Actions

Send email

The Send Email action lets you send an email directly from your test. This is useful for testing inbound email flows — for example, verifying that your app correctly processes an incoming support request, forwards a message, or triggers an automation when an email is received.
You must create an inbox before using Send Email. The email is sent from your SpurMail inbox address.
To add a Send Email step, select Send Email from the email actions menu. You will see three fields:
  • Email To — the recipient email address
  • Subject — the email subject line
  • Body — the email body content
The Send Email step in the test editor

The Send Email step in the test editor

Using your inbox email address

Inserting the email in test steps

You can insert the generated inbox address dynamically in your test steps in two ways: Method 1: Type @ anywhere in your test step where you want the email address to appear. This will automatically insert the current inbox email address.
Typing @ to insert the inbox email address into a step
Method 2: Access inbox-related variables through the variable menu by typing { and selecting from the test_account variable options.
Variable menu showing test_account inbox variables
A test step referencing the inbox email variable

Accessing your inbox on the web

You can also view your inbox directly in a web browser:
  1. During test execution: Use the Open Inbox action to open the inbox in a new tab
  2. In the Test Editor: Navigate to https://spurmail.com, type your inbox username (e.g. test_account) into the address bar, and press Enter—no extra browser action needed.
This is particularly useful for debugging email content, checking delivery status, or manually verifying emails outside of your automated tests.

Accessing email content

Once you’ve navigated to the spurmail.com inbox, you can access different parts of an email by clicking on the appropriate tabs in the email interface.
The options for each email

The options for each email

Tip: Use the Links tab to click on links within emails, such as verification links, password reset links, or any other clickable elements in your test emails.

Extract a value from an email

Use Read Latest Email, then add an Extract step that describes the visible value you need, such as an OTP code or confirmation number. In a later step, type { and select that extracted variable. Keep the email open while the Extract step reads it.

Get codes from an authenticator app

Use the SpurMail authenticator to test sign-ins that ask for a 6-digit code from an authenticator app, such as Google Authenticator or 1Password. Give it a test account’s setup key, and it shows the current code.

Get the setup key

When you turn on two-factor sign-in for a test account, your app shows a QR code. Most apps also show the setup key as text under the QR code, with a label such as “Can’t scan it?” Copy that key. If your app shows only a QR code, the setup key is inside it. Scan the QR code with a QR code reader that shows the decoded text. The text is a link like otpauth://totp/Example:qa@example.com?secret=JBSWY3DPEHPK3PXP&issuer=Example. The value after secret= is the setup key. In this example, it’s JBSWY3DPEHPK3PXP.
Anyone with the setup key can make valid codes for the account. Use the SpurMail authenticator only with test accounts, and don’t paste the key or the QR code into an online decoder. SpurMail doesn’t store the key, so save it in your password manager.

Open the authenticator

Go to https://spurmail.com/authenticator/ followed by the setup key, with no spaces:
The page shows Authentication Code and the current 6-digit code. Below the code, Refreshes in counts down to the next code. Click Copy Code to copy it. To finish turning on two-factor sign-in, enter this code in your app.

Enter the code in a test

1

Open the authenticator in a new tab

When the test reaches your app’s code field, add an Open New Tab step with your authenticator URL.
2

Extract the code

Add an Extract step that reads the 6-digit code under Authentication Code.
3

Go back to your app

Add a Close the Current Tab step. The test returns to your app’s code field.
4

Enter the code

In the step that fills in the code field, type { and select the extracted variable.
You can’t use an encrypted variable in the Open New Tab URL. The setup key shows in plain text in the test steps, on the test results page, and in shared test results, so anyone who can see them can make codes for the account. Use a test account that doesn’t protect real data, and share results only with people who can already sign in to that account.
The authenticator makes standard codes: 6 digits that change every 30 seconds. Most authenticator apps use this format. If your app uses other code settings, the codes don’t match. Because each code lasts 30 seconds at most, put the Extract step right before the steps that enter the code.

Example test

Here is an example for a test that types a randomly generated inbox into a field on the page and verifies the contents of the received email. Example test typing a generated inbox address and verifying the received email

Tips

Example use cases

Use SpurMail to:
  • User Registration: Test confirmation emails and verification links
  • Password Reset: Verify reset instructions and link functionality
  • OTP Verification: Test delivery and validation of one-time passwords
  • Marketing Emails: Verify promotional content and unsubscribe functionality
  • Transactional Emails: Test order confirmations, shipping notifications, and invoices
  • Multi-step Workflows: Automate processes that include verifying against an email

Helpful notes

  • You can use multiple email addresses in the same test
  • Add a Close and Clear Inbox teardown step so each run starts with an empty inbox.