Venom CLI
Venom runs YAML integration suites, executes HTTP requests and scripts, checks results and exports reports for CI.
- 1,226 ★ on the repository
- Last commit
- Apache-2.0
Extended access
Why this level
- Test executors run commands and requests with configured access and can change target-system data.
Install
Manual install
curl https://github.com/ovh/venom/releases/download/v1.2.0/venom.linux-amd64 -L -o /usr/local/bin/venom && chmod +x /usr/local/bin/venomFirst README binary-install example for Linux amd64, preserving its exact pinned version.
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- Test executors run commands and requests with configured access and can change target-system data.
This is third-party code. Review the repository files before installing.
What it does
Venom stores integration tests in YAML and executes steps through its CLI. The test author selects an executor, such as HTTP or a script, and defines assertions for each step. Venom runs it and checks the result against those assertions. Outputs can feed later steps. Variables and files separate environment data. Invocation controls suite ordering. Agents can prepare service checks and inspect reports while keeping tests reviewable as code.
Who it is for. Service-integration QA engineers defining requests, steps and expectations in readable YAML suites.
Good fit when
- An API scenario passes one step’s response to another.
- One integration test needs different environment parameters.
- CI requires XML or JSON results.
- A release needs a repeatable sequence across several services.
Not a fit when
- Tests use production access and can irreversibly change real data.
- You expect correct assertions without knowledge of the service.
- You only need static source analysis.
Example request
Prepare a YAML test for our test API: create a temporary object, read it and assert the response. Show cleanup before running.Limitations
Executors perform real actions, so test environments need agreed endpoints and permissions. Supply secrets through protected configuration rather than exposed arguments or shared reports. File order affects execution; list dependent suites explicitly. The README installation example pins Linux amd64 and version 1.2.0, so other platforms need an appropriate release binary and a compatibility check.
How to disable. Stop test execution and inspect spawned programs or external actions. Uninstalling does not clean up data created by tests.
FAQ
Where is a test defined?
In a YAML suite file. Version and review it with code.
How do I run one file?
Use `venom run mytestfile.yml` and review variables first.
How do I export JSON?
Use `--format=json` and `--output-dir`, then inspect before sharing.
Can I order suites?
Yes. Listed files run in the supplied order; avoid relying on discovery order.
How do I externalize parameters?
Use `--var-from-file` and separate secrets from shared examples.
Discussion
No questions or reviews yet.
Related
CLI toolsReviews the git diff and the conversation with the agent: catches bugs and gaps between your request and the agent's result. CLI, skill, GitHub Action
The CLI creates Python environments and repeats project build, install and test steps for agent-led compatibility checks.
A CLI from TestMu AI that writes end-to-end tests from requirements and runs them in a browser or on mobile, with a skill for your agent
Vercel CLI for testing coding agents on your framework: runs Claude Code, Codex and others and measures the success rate
The CLI runs QA Wolf flows locally and in CI, refreshes cached tests and helps investigate traces from failed attempts.
A skill that tests your agent's code in a real browser: reads your changes, builds a test plan and runs it through Playwright with your own cookies
README in short
Executors include scripts, web scenarios and IMAP alongside HTTP. xUnit-compatible output supports CI.