Email testing for developers and QA
Signup, verification, OTP and password reset are the flows most likely to break in production and the hardest to cover in a test suite, because they leave the app and come back through a mailbox. A disposable inbox closes that loop.
A typical end-to-end run
- Create a temporary mailbox and read its address.
- Register a test user with that address.
- Wait for the verification mail to arrive in the inbox.
- Extract the link or the one-time code from the message body.
- Continue the test with the verified account.
What to assert
Beyond “did it arrive”: check the sender and subject, that the verification link points at the environment under test, that the code has the expected shape, and that the message renders without a broken layout.
Programmatic access
A documented developer API with API keys and webhooks is on the roadmap. Until it ships, the web inbox is the supported interface — please do not scrape it in CI, as automated traffic is rate limited.