# Run your release tests against production

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.

## How to do it in Zerocheck

1. Prefer staging for tests with side effects.
2. If you need to test production, use dedicated test data and review every action.
3. Run the selected tests by hand, or on your own CI schedule.
4. Use your monitoring provider for continuous checks, alerting and incident response.

## Frequently asked questions

### Does Zerocheck send production incident alerts?

No. Run results are available in the web app and CLI, and there's no monitoring or alerting product.

### Can GitHub Actions run tests on a schedule?

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.

---
Canonical: https://tryzerocheck.com/use-cases/production-monitoring/
Updated: 2026-11-01