CI/CD with the Operio CLI
Run a test or a suite from GitHub Actions, GitLab CI, Jenkins or any other pipeline. The CLI waits for the result, prints JSON, and fails the job when a test fails.
- Runs on
- Any CI with Node.js 18+
- Output
- JSON on stdout
- Gate
- Fails the job when a test fails
How it gates a pipeline
A pass or fail your pipeline already understands
- 01
Waits for the verdict
With --wait, the command blocks until the run finishes, so the next stage only starts once the tests are done.
- 02
Fails the job on failure
A passed run lets the job carry on, and a failed test stops it, so a broken release doesn't go out.
- 03
JSON on stdout
Every command prints JSON, so a later step can post a summary, link the run, or decide what to do next.
Setup
Set up CI/CD in minutes
- 1
Install the CLI in the job with npm install -g @operio/cli.
- 2
Run operio suites run with your suite and environment IDs, plus --wait.
- 3
Let the result pass or fail the job, and keep it for later steps.
FAQ
CI/CD questions
Any provider that can run Node.js 18 or newer: GitHub Actions, GitLab CI, CircleCI, Jenkins, Buildkite and others.
Yes. Upload the build with the CLI, then run tests against it.
The CLI exits with code 1 and prints the run result as JSON, including which tests failed.