Turn your release checklist into browser tests

Paste the tests your team performs before a release. Zerocheck drafts and runs one independent browser test per top-level checklist item, then lets you review the results and save the tests you want to keep.

Write one flow and outcome per item

A short sentence can be enough when it includes the action and expected result. For a detailed flow, indent its steps beneath the top-level item. Headings and lines starting with Note: provide context; they do not become tests.

Here is an example to adapt to your own app and existing test data:

# Release smoke tests
Note: A product named Notebook exists in the test environment.

- Search finds a product
  Open the app.
  Search for "Notebook".
  Verify text "Notebook" is visible.

- The help page is available
  Open /help.
  Verify text "Contact support" is visible.

This checklist produces two tests. Each starts independently, so the second test must not depend on state created by the first. Include any setup each flow needs, or configure reusable login steps for the environment.

Preview, run and review

1. In the web app, choose Import checklist.
2. Paste text or upload a .md or .txt file, up to 64 KB and 200 items.
3. Check the preview to confirm which lines belong to each test.
4. Start the import. Each executable draft runs in the hosted browser.
5. Inspect the steps, result and evidence for each item.

The review states are Draft · not verified, Verified passing, Check failed, Needs input, and Could not run. A missing credential is something to resolve; it is not proof that your product failed. Unsupported tasks remain visible for your review.

Keep control of the expected result

Use Edit steps when a draft does not express the flow you intended. Supply missing details together, then use Run drafts again. Keep the expected outcome specific: a particular total, destination, label or state is more useful than “everything works”.

Choose Save this test or save the selected group to Your tests. You can retain failing tests to reproduce a known issue; saving does not make them pass. Unfinished imports remain in Recent drafts.

Use imported tests in a repository

Checklist import is in the web app; the CLI has no import command. To run a saved test from your repository, use Download YAML on that test and follow the CLI quickstart. The download is an independent copy, and edits do not synchronize.

Create one test instead · Read the test format · Inspect results