# Test the browser flow around an email handoff

Test the sign-up, reset and confirmation pages around an email with a prepared account. Keep inbox and SMS checks in your integration tests.

It's easy to treat a visible "Email sent" message as proof that delivery, the link and the next page all work. A success message doesn't prove an email arrived, and link expiry and one-time use need controlled test data.

Use a browser test for the request form and its visible response. Verify delivery and token handling separately, and test the resulting app state with a prepared account.

## How to do it in Zerocheck

1. Separate what the browser can show from email delivery and token verification.
2. Configure a test account that can use a supported login path.
3. Draft a browser test for the form, validation and visible confirmation.
4. Keep inbox polling, magic-link extraction and SMS flows in your existing integration tests.

## Frequently asked questions

### Can Zerocheck open a magic link from an inbox?

No. It doesn't read inboxes or SMS messages, so keep those checks in your integration tests.

### What browser coverage is useful here?

Form validation, visible request confirmations and post-login app behavior, with suitable test data. A browser test doesn't show that the email arrived, so check delivery separately.

---
Canonical: https://tryzerocheck.com/use-cases/email-flow-testing/
Updated: 2026-11-01