Testing
Go workspace
This repo uses ago.work workspace that aggregates the modules under agents/ and tools/.
Running go test ./... from the repo root will fail because the root directory is not itself a module.
Running tests
Use the repo test runner from the root:go test across the workspace modules listed in go.work.
Make sure the Go toolchain is installed and on your PATH before running tests.
The script expects to be run from the repo root so it can find go.work and will
error with a short message if prerequisites are missing.
Use ./tools/test.sh --help for a quick usage reminder.
Use ./tools/test.sh --list to print the module list without running tests.
Use SI_GO_TEST_TIMEOUT=20m ./tools/test.sh to adjust the go-test timeout when needed.
For one-command local coverage of the standard test stack, run:
Plugin runner matrix
For plugin-system specific regression lanes (inspired by OpenClaw’s segmented CI), use:Installer smoke tests
To validate thesi installer script end-to-end, run:
./tools/test-install-si.sh --help for a quick usage reminder.
Vault strict suite
Run the dedicated strict vault suite:SI_INSTALL_SMOKE_SKIP_NONROOT=1 ./tools/test-install-si-docker.sh to skip
the non-root leg during local iteration.
CI notes
GitHub Actions workflows use docs-only change detection to skip heavy test jobs when only docs/markdown files are modified.PaaS matrix
Forsi paas quality-gate coverage (unit/integration/e2e regression matrix), use:
Static analysis
Run static analysis from the repo root:./si analyze:
CLI help smoke checks
After CLI command-surface changes, run targeted help checks:Image build smoke check
si build image now runs a Codex compatibility preflight (dyad/spawn/mount/MCP
lanes) before building the image.
Run the preflight directly:
