Break magic-link testing into the request form, email delivery, token handling and authenticated app state. Each part needs its own evidence.
The request form can show the right state while delivery fails. The email can arrive while its token is unusable. Keeping these assertions separate makes the failure actionable: the browser test covers the form, and the email or authentication test covers the handoff.
Email, SMS and magic-link-in-email steps are unsupported. If your only login path requires an inbox interaction, resolve that setup constraint during the evaluation before expecting an authenticated browser suite to run.
No. Use a separate email harness. Zerocheck does not provide inbox access or magic-link extraction.
Yes, when you provide a supported login setup and test account. The browser test then covers the specified app behavior.
Describe a customer flow or paste your release checklist, review the browser result, and save the tests you want to rerun.
Get a demo