CI/CD

Browser test results on GitHub pull requests

Run your saved YAML tests in GitHub Actions with the Zerocheck CLI. One PR comment links the result to the full browser run.

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.

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

Authenticate the CLI and generate a workflow with zerocheck init --github-actions.

Configure the project token, staging URL and test-account credentials.

Run repository tests on pull requests; the workflow reports results and uploads artifacts.

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

One PR comment updates in place with passed, failed, flaky and healed results.
Full results include exact YAML, step screenshots, errors and every attempt.
Nonblocking failures remain visible while the CLI respects each test’s merge policy.
Local CI browsers still use Zerocheck’s AI service and upload results to the web app.