OpenClawDocs
On this page

On this page

View as MarkdownView this page as plain textOpen in ChatGPTAsk questions about this pageOpen in ClaudeAsk questions about this page

Testing and CI

Tests

For proof selection, follow the canonical proof policy.

This page is an index. The testing reference is documented on six pages, one per reader job. Open the page that matches your task.

Page Read it when
Run tests locally The routine local order, the core command table, and the local PR gate.
Control UI, TUI, and E2E lanes Control UI, TUI, extension, Gateway, and live lane commands and fixture rules.
Docker test suites The weighted Docker scheduler, its knobs, and the notable Docker lanes.
Test performance and benchmarks Import profiling, CPU and heap profiles, shard timings, and the benchmark scripts.
Test runner internals Shared build locks, isolated test state and homes, and JSON report merging.
Remote test proof When agents use Crabbox or Testbox, and the wrapper, lease, and trust rules.

Local command guidance

For ordinary local tests, start at docs/reference/test.md#routine-local-order (routine local order) and #core-commands; read CI when scope or runner behavior matters. Follow the touched subtree's AGENTS.md.

pnpm verify runs the full check and then test when that scope is justified. For worker-sensitive failures, OPENCLAW_VITEST_MAX_WORKERS=1 pnpm test <path> provides a focused serial probe; do not make a forced environment the repair. Inspect changed checks with node scripts/check-changed.mjs --dry-run -- <paths...> before running the selected plan.

Where each section moved

Every section heading from the previous single-page version keeps its anchor here, so an existing link such as /reference/test#core-commands still resolves. Each entry points at the page that now holds the content.

Was this useful?