Template variables

Replaying a signup with a hardcoded email works exactly once — the second run hits "account already exists." The fix isn't editing the suite before every run; it's letting the values generate themselves.

Variables resolved at replay time

Type a template variable anywhere a step takes input and it's substituted the moment the step runs:

• {{testEmail}} — a unique Mailsac inbox, so email steps can poll it.
• {{randomEmail}} — a throwaway address when you don't need to read the mail.
• {{randomHash}} — a short random token.
• {{uuid}} — a v4 UUID.
• {{randomInt}} — a random integer.
• {{timestamp}} — the current epoch in milliseconds.
• {{randomPhone}} — a random phone number.

They work in value, selector, and url fields alike — the same syntax everywhere a step accepts input.

Why it matters

Because every run gets its own data, replays stay idempotent: run the suite a hundred times, on a schedule or in parallel, and no two runs step on each other's records. That's what makes scheduled runs and multi-session tests safe to fire repeatedly without a cleanup script between them.