Test Workflow
Exercise campaigns, workflows, and transactional sends on fixture addresses without hitting real inboxes, bounces, or complaints.
Use fixture recipients when you want the full send path — render, queue, Emails list, workflow run — without SES leaving Lumail. That keeps complaints and bounces off your sending domain.
A dry run is different: it skips email steps entirely. Fixture sends go through the real dispatcher and are recorded as sent.
Fixture addresses
Any of these is auto-faked. The email is accepted, stored, and marked sent. SES is never called.
| Pattern | Example |
|---|---|
example.com, example.net, example.org, including subdomains | [email protected], [email protected] |
test.com, test.net, test.org, test.dev, including subdomains | [email protected], [email protected] |
Special-use TLDs .test, .example, .invalid, .localhost | [email protected], [email protected] |
Local-part starts with playwright-test- (any domain) | [email protected] |
Display names are stripped first (Ada <[email protected]> is still a fixture).
Do not use a real mailbox ([email protected], your own domain). Those still go to SES when sending is enabled and can bounce or complain.
example.edu and lookalikes such as contest.com or mytest.com are real domains and still send.
Workflow
- Create a subscriber with a fixture address, for example
[email protected]. - Give them the tags, fields, and revenue the graph actually reads.
- Publish the workflow, then enroll that subscriber (trigger or manual enrollment).
- Open the run timeline. Email steps execute instead of skipping.
- Open Emails — the row is there, status is sent, and nothing hit a real inbox.
Repeat with one fixture subscriber per important path (welcome, branch A, exit, goal).
Campaigns, API, SMTP
The same gate is shared:
- Campaign Send test email
- Broadcast and workflow campaign sends
- Transactional HTTP and SDK
- SMTP
Send to [email protected] or [email protected] from any of those surfaces.
What you get / what you do not
| Happens | Does not happen |
|---|---|
| Render, personalization, unsubscribe link | SES API call |
| Queue, journal, Emails list | Inbox delivery |
| Workflow run continues past the email step | Bounce or complaint events |
| Recorded as sent | Reputation impact on your domain |
You still need one real send to yourself (or a mailbox you control) if you want to inspect the inbox, spam folder, or rendering in Gmail / Apple Mail.
Related
- Test-mode recipients — exact match rules
- Workflow Test Runs and Results — dry runs with no email side effects
- Email Step
- Send Transactional Email