# Keep release tests and incident monitoring clear

Zerocheck runs browser tests against configured environments, including production. It does not provide an incident-monitoring or alerting service.

Zerocheck runs browser tests against configured environments, including production. It does not provide an incident-monitoring or alerting service.

## Who it is for

- Role: Engineer responsible for releases
- Company: Teams with an existing monitoring stack
- Trigger: The team wants to verify a user flow after deployment

## Why this is underserved

- A browser test verifies one flow at one point in time.
- Incident detection needs scheduling, alert routing and an operating response.
- Production test actions can change real application state.

## The workflow

Before: The team expects a release-test result to act like an always-on monitor.

After: Use Zerocheck for a deliberate test run with dedicated test accounts. Keep uptime checks, incident alerts and on-call routing in the monitoring system you already operate.

## How Zerocheck handles it

1. Prefer staging for tests with side effects.
2. If production testing is necessary, use dedicated test data and review every action.
3. Run the selected tests manually or through your own CI schedule.
4. Use your monitoring provider for continuous checks, alerting and incident response.

## Good fit when

- A web app and a repeatable user flow
- A test environment, test accounts and an explicit expected outcome

## Frequently asked questions

### Does Zerocheck send production incident alerts?

No. Run results are available in the web app and CLI; there is no production-monitoring or alerting product.

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

Yes. Configure your own Actions schedule and choose the environment. A scheduled browser test still does not supply incident management.

---
Canonical: https://tryzerocheck.com/use-cases/production-monitoring/
Updated: 2026-09-14