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.
Separate what the browser can show from email delivery and token verification.
Configure a test account that can use a supported login path.
Draft a browser test for the form, validation and visible confirmation.
Keep inbox polling, magic-link extraction and SMS flows in your existing integration tests.
Paste your QA checklist. Zerocheck drafts editable browser tests, runs them in your app, and shows the result of each item before you save it.
Zerocheck keeps the test, its step screenshots and its errors together, so an engineer can explain a browser test result.
Start with a browser test in the web app, then use the optional CLI to run repository YAML in a CI job and act on its exit code.
No. It doesn't read inboxes or SMS messages, so keep those checks in your integration tests.
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.
US$500 in credits at sign up, with a dedicated instance and hands-on onboarding.
Book a setup call