CI/CD

Run browser tests in GitHub Actions

Run your saved YAML tests in a GitHub Actions job you write, with the Zerocheck CLI. The exit code fails the job, and a results link opens the full browser run.

Book a setup call

The problem

A pull request needs more than a red or green job. The reviewer needs the expected outcome, the failing step and the test revision that actually ran.

How it works

1

Draft and verify a browser test in the web app, then download its YAML into your repository.

2

Write a workflow that installs the CLI and Chromium. The docs include an example.

3

Configure ZEROCHECK_API, a project token, your environment URL and test-account credentials.

4

Run repository tests on pull requests; a blocking failure exits non-zero and fails the job.

5

Require the Actions job in branch protection if blocking failures should stop a merge.

What you get

  • The exit code is the integration: 0 every blocking test passed, 1 a blocking failure, 2 no verdict.
  • Full results on your instance include the steps that ran, their screenshots and any errors.
  • A nonblocking test's failed outcome stays visible without failing the job.
  • Your instance makes every decision and keeps the results.
Browser Tests in CI →

Other integrations

Try it on your own app

US$500 in credits at sign up, with a dedicated instance and hands-on onboarding.

Book a setup call