Test inbox capture

Mailosaur gives disposable inboxes that catch the email and SMS your application sends during testing. A Beam agent watches a test run, reads the messages that land in the test inbox, and checks them against what your rule expects, such as a specific sender, subject, or arrival within a time window. It records each check as pass or fail on the run. A message that never arrives, or one that lands but does not match, is flagged for a person, since a missed test email often signals a real problem in the flow being tested rather than a testing error.

Content and code verification

Messages caught by Mailosaur can be examined for their exact content, including links and one-time codes. A Beam agent reads the captured message, pulls the value your rule points to such as a verification code or reset link, and confirms it matches the expected pattern. It writes the result to the test record and can pass the extracted value to the next test step. Content that fails the pattern, or a code the agent cannot locate where it should be, is routed to a person, because a broken code or link points to a defect worth a human look.

End-to-end flow testing

Mailosaur supports checking full flows like sign-up, password reset, and two-factor login where a message is part of the path. A Beam agent runs the flow, waits for the expected message, reads it, and confirms the whole sequence completed under your rules before marking the flow healthy. It records each step's outcome. A flow that stalls, produces an unexpected message, or completes with the wrong details is handed to a person, so a failing customer-facing path is investigated rather than quietly recorded as a passing run.