Zerocheck can test supported browser actions before or after an email handoff. Inbox retrieval, email links and SMS verification need a separate test harness.
Browser form and confirmation tests
Email delivery needs a separate harness
Prepared accounts for downstream flows
A success message does not prove that an email arrived.
Link expiry and one-time use need controlled fixtures.
Inbox access and browser interaction are separate parts of the test.
The team treats a visible “Email sent” message as proof that delivery, the link and the next page all work.
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 the browser-visible expectation from email delivery and token verification.
Configure a test account that can use the 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 exact test revision, step screenshots, errors and attempts 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 GitHub Actions and post a result on the pull request.
No. Email retrieval, magic-link-in-email and SMS steps are unsupported.
Form validation, visible request confirmations and post-login app behavior can be tested with suitable fixtures. These results do not establish email delivery.
Zerocheck can test supported browser actions before or after an email handoff. Inbox retrieval, email links and SMS verification need a separate test harness.
Get a demo