MailSlurp gives engineering and QA teams a stable way to test messaging-critical journeys before production.

High-value workflows to cover

1. Signup confirmation and magic-link authentication.
2. Password reset and account recovery notifications.
3. OTP, 2FA, and MFA code delivery over email and SMS.
4. Transactional notifications that must arrive quickly and correctly.
5. Webhook-driven automations that depend on inbound message events.

Reference implementation pattern

1. Create an isolated inbox and (optionally) a test phone number.
2. Trigger your application flow.
3. Wait for the matching message using message criteria.
4. Extract links/codes/content and assert expected behavior.
5. Fail fast on timeout, malformed content, or routing mismatch.

CI reliability controls

• Use one inbox per test run or worker.
• Prefer API wait primitives over static sleeps.
• Keep explicit timeout budgets by flow type.
• Persist inbox/message IDs in test artifacts for debugging.
• Add webhook assertions for asynchronous systems.

Add ownership and escalation layers

Integration tests catch defects earlier when message handling ownership is explicit:

• Use Team mailboxes for shared review queues after failed CI runs.
• Add Email auto-reply policies for controlled acknowledgement and exception routing.
• Attach Messaging webhooks so downstream systems can react without polling.

Email, SMS, and TOTP coverage

• Email assertions: subject, sender, links, headers, attachments.
• SMS assertions: OTP format, delivery timing, fallback behavior.
• TOTP assertions: virtual authenticator setup and rolling-code checks.

For TOTP-specific implementation, see virtual authenticator devices.

Related routes

• Email Sandbox
• Email testing product
• SMS products
• Testing category
• Cypress email testing guide
• Playwright OTP guide

Next step

Start with Email Sandbox for safe capture, then wire assertions from this page into your CI release gates.