# Keep the test result next to what actually ran

Zerocheck keeps the exact test revision, step screenshots, errors and attempts together so an engineer can explain a browser test result.

Zerocheck keeps the exact test revision, step screenshots, errors and attempts together so an engineer can explain a browser test result.

## Who it is for

- Role: Engineering lead
- Company: Teams that need to review release testing
- Trigger: A reviewer asks what was tested on a particular change

## Why this is underserved

- A green CI job does not explain which user outcome was verified.
- Screenshots lose context when separated from the test and environment.
- Test results are useful engineering records; audit conclusions require a separate review.

## The workflow

Before: Someone assembles screenshots and job output after a release, then tries to reconstruct the steps and environment.

After: Open the run to see the exact YAML, environment and per-step result. CLI uploads can include the repository, commit and pull request that triggered the run.

## How Zerocheck handles it

1. Write a test with a specific expected browser outcome.
2. Inspect the run in the web app, including every step and attempt.
3. Use CLI JSON output when another process needs the run record.
4. Have the responsible reviewer decide how the record supports their own release process.

## 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 produce SOC 2 evidence packages?

Zerocheck provides browser test results. It does not map controls, certify compliance or provide an audit evidence export workflow.

### Is there a recording for every run?

Screenshots are captured before and after each step. A recording is available when the test uses no configured credentials.

---
Canonical: https://tryzerocheck.com/use-cases/soc2-evidence/
Updated: 2026-09-14