Test email signup flows without losing track of the messages.

Separate application, delivery, and browser checks

At the application layer, assert that the right event requests the right message. Laravel’s mail testing tools can prevent real sending and let tests inspect what would have been sent. That verifies application behavior; it is not evidence of successful internet delivery.

For local delivery checks, an SMTP capture tool such as Mailpit receives messages for inspection. Its API supports automated workflows. For a final manual browser check, an inbox helps you see the experience from the recipient’s side. Keep these results separate so a passing unit test is not mistaken for a successful end-to-end delivery.

Start with a small, meaningful test matrix

Use a distinct test address for each concurrent scenario, then record which account and request it belongs to. This avoids opening one test’s message while evaluating another. Include a recognizable identifier in your own application’s test data where appropriate.

The goal is to exercise behavior that can fail, not merely check that some email exists. Verify the recipient, subject, link destination, and state after the recipient acts.

• Fresh signup: one expected verification message reaches the intended address.
• Resend: the interface follows the documented retry interval and code behavior.
• Expired link: the user gets a clear explanation and a valid next step.
• Repeated link: completing verification twice does not corrupt account state.
• Mistyped address: the user can correct it without an unexplained dead end.
• Password reset: the request and completion behave correctly for the test account.

Make a manual inbox check reproducible

Create the inbox before submitting the form. Record the test time and exact recipient. Complete the flow while the inbox is active. Inspect whether the message is readable on a narrow screen and whether its primary action takes you to the expected environment.

If the message does not arrive, check your application queue and mail logs, then confirm the recipient and receiving path. This inbox has no built-in test message, so a short email from another mailbox you use is the quickest check that the address receives mail.

Keep automated tests under your control

For continuous integration, prefer a controlled capture inbox with an API and predictable cleanup. Poll for a specific recipient and message with a bounded timeout. Avoid relying on a fixed sleep or on the newest message in a shared inbox.

Use synthetic names and content, and keep real customer data out of test messages. Test only applications and accounts you are authorized to test. For automated runs, this site’s Developer Mail API and MCP server create a disposable inbox, wait for the next message, and return its codes, links and attachments; the test data generator makes synthetic JSON or CSV records to fill your forms.

Common questions