Reflect handles browser automation. MailSlurp handles private inbox creation and message assertions.

Used together, they provide a no-code-plus-API workflow for testing real signup verification behavior.

Architecture in one view

LayerToolResponsibility
Browser journeyReflectDrive signup UI and submit generated address
Inbox controlMailSlurpCreate isolated inbox per test run
Verification evidenceMailSlurp APIWait for email, extract code or link, assert payload
Completion checkReflectContinue flow and validate account activation

End-to-end runbook

  1. Create a fresh inbox for this run.
  2. Use Reflect to submit signup with that address.
  3. Poll or wait for verification email via MailSlurp.
  4. Extract verification code or link from the email.
  5. Continue the Reflect flow and confirm activated state.

This removes the common blind spot where teams only test form submission and not actual message behavior.

Demo resources

For a sample journey, use .

test interface sample app signup step verification code

Assertions worth keeping in your baseline

  • Sender identity and environment routing correctness.
  • Subject and template variant correctness.
  • Verification token format and expiry behavior.
  • Maximum acceptable email delivery latency.

Failure drills to add once baseline is green

  1. Delayed delivery simulation: verify timeout behavior is explicit.
  2. Broken-link simulation: assert activation fails for malformed links.
  3. Wrong-template simulation: ensure mismatch is caught before release.
  4. Parallel-run simulation: confirm inbox isolation avoids cross-test leakage.

These drills improve confidence more than adding extra happy-path checks.

For implementation details and SDK references, see MailSlurp developer docs.