Zerocheck runs browser tests against the environments you configure, including production. Keep your existing monitoring for alerts and incidents.
A release test isn't an always-on monitor. It checks one flow at one point in time, while incident detection needs scheduling, alert routing and someone on call.
Use Zerocheck for a deliberate test run with dedicated test accounts, and keep uptime checks, incident alerts and on-call routing in the monitoring system you already operate. Test actions in production can change real application state, so prefer staging for anything with side effects.
Prefer staging for tests with side effects.
If you need to test production, use dedicated test data and review every action.
Run the selected tests by hand, or on your own CI schedule.
Use your monitoring provider for continuous checks, alerting and incident response.
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. Run results are available in the web app and CLI, and there's no monitoring or alerting product.
Yes, in a job you write. Zerocheck has no built-in scheduler, so configure your own Actions schedule and choose the environment. That still doesn't give you incident management.
US$500 in credits at sign up, with a dedicated instance and hands-on onboarding.
Book a setup call