Glossary
CI/CD testing runs automated tests as part of integrating and delivering software changes. Different stages can execute different tests against suitable environments.
Automated execution creates a consistent place to check a change before release. The result is useful only when environment setup, test data and failure handling are reliable.
Teams keep fast lower-level tests early in the pipeline, run selected browser flows against a deployed environment and preserve artifacts even when a job fails.
The optional Zerocheck CLI runs repository YAML in a CI job you write and can write a JSON run record. Results and evidence are kept on your instance and appear in the web app.