Test sign-ups that send an email or SMS code
A sign-up form that submits is not a sign-up that works. Give the test its own mailbox or phone number and check the whole journey, code included.

The part of sign-up nobody tests#
Most sign-up tests stop at the form. They fill in an email address, press the button and check for "We sent you a confirmation email". Then they pass.
Everything that breaks in real life comes after that sentence. The email never leaves. It leaves with a link to the wrong environment. The code has expired by the time it arrives. The link works and the account is still marked unverified. None of that is visible on the page that says the email was sent.
It gets skipped because it is awkward to automate: a test needs an inbox nobody else is using, a way to read it, and a way to get the code back into the browser. This post shows how to hand all three to the tester.
Give the run its own mailbox#
In a test's options, turn on Give this test a mailbox. Each run then gets an email address of its own, signs up with it, waits for your app's message and follows the link or types the code. It is included on every plan, the free trial too.
Write the test the way you would brief a person:
Create a new account using this run's email address and a test password.
Submit the sign-up form and check that it asks the user to confirm their email.
Wait for the confirmation email and open its link.
Check that the app says the email is confirmed and shows the new account's workspace.
Reload and check that the account is still signed in and usable.
Do not invite anyone or enter payment details.
Because every run gets a fresh address, you never hit "this email is already registered" on the second run.
To see it done, Test email verification codes, the wrong code and the resend too has two real runs with their results and videos: a wrong code refused, the real one read from the email, and a first code that stops working once a second is requested.
Two details save time:
- Run addresses end in
@inbox-test-engine.testsy.dev. If your staging sign-up only accepts certain email domains, allow that one. - Adding
+somethingbefore the @ reaches the same mailbox, for tests that need two addresses, such as inviting a second user.
Codes by SMS, and phone calls#
For a code sent by text message, turn on Give this test a phone number. The run gets its own number, reads the SMS your site sends and enters the code. It can also take a phone call and press keypad digits during it, for flows that read a code aloud or ask you to press 1 to confirm. The phone number is on paid plans. For a text message that arrives on a phone and is handed to an app, see Test SMS code sign-in on Android, which has a real run.
Sign up with this run's phone number.
Wait for the SMS code and enter it.
Check that the app shows the phone number as verified.Check the message as well as the screen#
After the run, the result has a Messages tab. It lists every email, SMS and call the run received, in order: who it was from, the subject, the text, the codes and links found in it, and the step where the tester used it. A check that was decided on a message links to that message.

So when a sign-up test fails, you can tell which half failed. The replay shows what the browser did. Messages shows what your app actually sent, and when.
Messages can hold links that still work, so only members of your workspace see them. A share link to the result leaves them out.
When it does not pass#
| What you see | Where to look |
|---|---|
| The form rejects the run's address | Your staging rules for email domains. Allow the run domain above. |
| The app says it sent a message and none arrives | Your mail provider's delivery log and the sender set-up for that environment. The notice on screen proves nothing. |
| The message arrives and the link will not open | The link's host. A link that points at a developer's machine cannot be opened from our browser. |
| A challenge stops the sign-up | Your bot protection on staging. A run the site stops is not a verified sign-up, and blocked runs are not counted. |
| The tester cannot tell whether the account is verified | The check. Name the visible thing that shows it: a badge, a banner, the workspace name. |
A missing email is a failed check, never an assumed success. That is the point of testing it.
Keep it clean#
- Use a staging environment and made-up details. The test creates a real account in whatever environment you point it at.
- The run's address and number stop receiving messages when the run ends.
- The test does not delete the account it made unless you write that into the steps. Decide who cleans up staging.
Run it on every release#
Once the test passes reliably, it belongs in the pipeline. A broken sign-up is the most expensive bug a product can ship quietly, because the people it affects never get far enough to tell you.
Start from the editable sign-up and email test, read the longer reference in Test signup and email verification, then add it to GitHub Actions or a nightly schedule.
Filed underWebSign-in and codes