<!-- GENERATED by docs/scripts/gen-cli-reference — DO NOT EDIT.
Source of truth: the cobra command definitions in cmd/axiom/cmd/.
Regenerate from the repo root with: go run ./docs/scripts/gen-cli-reference -->
axiom test
Run language-native tests with axiom validation
Run the language-native test suite after validating the axiom package.
Steps:
1. Compile proto bindings (axiom generate)
2. Validate package (axiom validate — fail fast on errors)
3. Run tests (language-native runner, output streamed live)Exit code mirrors the test runner exit code.
For Python packages, dependencies pinned in requirements.txt are staged
into .axiom/pydeps and put on PYTHONPATH for the run, so a node that
imports a third-party library is testable without a manual install. Your
site-packages are never modified; the staging is cached until
requirements.txt changes; an already-activated virtualenv wins. If pip
cannot run (offline, or no interpreter), axiom test warns and runs the
tests against the interpreter as-is.
Pass extra arguments to the native runner after --:
axiom test -- -v (Go: verbose output)
axiom test -- -run TestProcessOrder (Go: run a specific test)
axiom test -- -k test_process_order (Python: filter by name)
axiom test -- --testNamePattern Foo (TypeScript: filter by name)Usage
axiom test [-- <native-args>] [flags]Flags
| Flag | Shorthand | Type | Default | Description |
|---|---|---|---|---|
--help | -h | bool | help for test |
See also
- axiom — Axiom CLI — build and push node packages
- Guide: Create a node (Python)
- Guide: Create a node (Go)
- Guide: Create a node (TypeScript)
- Guide: Create a node (Rust)
- Guide: Create a node (Java)
- Guide: Create a node (C#)
Related