Skip to main content

​
Email & codes

Most sign-up and login flows send an email — a verification code, a magic link, a “confirm your account” button. TestBrick has its own inboxes so your tests can read those emails.

​
The easy way: let Bricklayer handle it

Write the flow and leave out the email address:
When a form asks for an email, Bricklayer types a TestBrick inbox address. When the app sends a code or link, it opens the email, takes the code or clicks the link, and saves those steps into your test.

​
Every run gets a fresh inbox

With the test’s Email setting on Dynamic (the default for new tests), each run types a brand-new inbox address. That means:
  • sign-up tests never fail with “email already registered”
  • each run reads the code from its own email, never a stale one
Switch Email to Static in the test’s Settings for logins, where the same address is the point. If you give an address in your brief (for example your own account’s email), Bricklayer types exactly that address.

​
Email steps

These steps appear in tests that use email: The code or link is read fresh on every run — from the inbox address that run typed.

​
Codes in split boxes

Many apps show a one-time code as six separate boxes. TestBrick types each digit into its own box, just like a person would.
Codes from an authenticator app (not email) are different — store the app’s key as a Secret and TestBrick makes the code itself.