Turn sign-in, onboarding, search and account-settings checklists into browser tests your team can review and run.
The team checks the happy path on release day but misses the account-settings flow affected by a shared component. Shared components can affect several customer journeys at once, and every new feature adds another item to the release checklist.
A saved suite repeats the customer journeys you choose. When one fails, you can open the failed step and see its screenshots. Failures are easier to act on when the expected outcome is explicit.
Choose a few flows already in your release checklist.
Prepare a test account and test data for each independent test.
Draft, review and save the tests in the web app.
Add CLI runs to an existing CI job when you want its exit code to gate a release.
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. Use browser tests alongside unit tests, integration tests and exploratory testing.
Use the optional CLI for localhost and private networks. Your instance makes the decisions and keeps the results.
US$500 in credits at sign up, with a dedicated instance and hands-on onboarding.
Book a setup call