Start with a browser test in the web app, then use the optional CLI to run repository YAML in GitHub Actions and post a result on the pull request.
Repository YAML through the optional CLI
A generated GitHub Actions workflow
One PR comment with full-result links
CI needs a usable test environment and reliable test data.
A merge gate is only useful if the team can investigate a failure.
Adding more tests helps when each one verifies behavior the team cares about.
The pull request passes unit tests, but someone still has to open staging and check the main flow by hand.
A saved browser test runs against staging in GitHub Actions. One PR comment links to the full result, including the failing step when a test fails.
Draft and verify one important flow in the web app.
Download its YAML, add it to your repository and authenticate the CLI.
Generate a GitHub Actions workflow with zerocheck init --github-actions and configure the project token and environment.
Choose blocking tests, require the workflow in branch protection, and inspect failures from the PR result.
Paste your QA checklist. Zerocheck drafts editable browser tests, runs them in your app, and shows the result of each item before you save it.
Zerocheck keeps the exact test revision, step screenshots, errors and attempts together so an engineer can explain a browser test result.
Turn your manual checkout checklist into browser tests. Evaluate the actual success and decline outcomes in test mode, locally or hosted.
The CLI exits non-zero for a blocking failure. Your GitHub branch-protection rules must require the workflow; the comment itself does not gate merges.
The local browser can run on your CI runner. It still uses Zerocheck’s AI service and uploads results and artifacts to the web app.
Start with a browser test in the web app, then use the optional CLI to run repository YAML in GitHub Actions and post a result on the pull request.
Get a demo