Create your first test in the web app

Describe one customer flow, run it in a hosted browser, inspect the result and save it for your next release. You can author and run tests in Zerocheck without installing a dependency or connecting a repository.

Before you start

You need access to a provisioned Zerocheck instance, a web app URL the hosted browser can reach, and an expected outcome for your first test. The seven-day assisted evaluation includes a setup call. Localhost requires the local CLI runner.

Choose a simple flow with existing test data. For example: open your app, search for a known product, and verify that its name appears in the results. If it needs login, configure reusable login steps and credential references with your instance owner first.

1. Choose your environment

In Settings, configure your project and its environment URL. The available environments are dev, staging and production. Use a test environment and test accounts for your first flow.

The environment supplies the starting URL, optional login steps and credential references. These are reused when the test runs; you do not need to paste a password into the test description.

2. Add a test

Open Add a test and enter:

• Test name: a short label, such as “Search finds a product”.
• What should the user do? The actions, page, controls and data that matter.
• Expected outcome: the visible result or state that must be true.
• Setup or test data: any necessary existing fixture or account information.
• Environment: where to run this draft.

Select Draft and run test. Zerocheck drafts the browser steps and runs them immediately in the hosted browser. Review happens after this first execution, so use an environment in which those actions are appropriate.

3. Inspect the result

Read the drafted steps alongside the browser result. Confirm that the actions and expected outcome match your intent. Use Edit steps to correct a draft, then run it again.

If the draft needs an account, a route or an expected outcome you have not supplied, answer the missing details and rerun. If it failed, inspect the failing step and its screenshots. See result states for the distinction between a failed outcome and a test that could not run.

4. Save and rerun

Choose Save this test to add it to Your tests. You can run one test, selected tests or all saved tests against a chosen environment. Edit the name and steps when your intended behavior changes, then run the new revision.

You can save a failing test to reproduce an issue. Saving it does not change its result to passing. An edited test needs a new run before that revision can have a passing result.

Take a test into your repository

Use Download YAML on an individual saved test. That creates an independent copy for your repository; it does not establish automatic synchronization. Web-created tests are edited in the web app, while repository-managed tests are edited in their files.

Import several tests at once · Use the CLI · Understand results