Skip to main content
Version: 0.1.78

Testing

X07 includes a built-in test harness designed for agents.

Test command​

  • x07 test (unit tests; manifest entries where pbt is not set)
  • x07 test --pbt (property-based tests only)
  • x07 test --all (unit + property-based)

Each test declares an execution world (typically run-os).

Output is an x07test JSON report including:

  • pass/fail summary
  • failures with diagnostic codes
  • failure classification (failure_kind, for example contract_violation)
  • resolved entry_kind for each test entry
  • optional mem_stats / sched_stats
  • sandbox evidence when present: sandbox_backend, runtime_attestation, effect_log_digests, and capsule_ids

See also:

Selection and debugging​

  • Filter by test id:
    • x07 test --filter golden_prm_signed_200 (substring match)
    • x07 test --filter golden_prm_signed_200 --exact (exact id match)
    • By default, filters that select 0 tests are an error; pass --allow-empty to treat “0 tests selected” as success.
    • Use --list to print selected tests without running them.
  • Per-test fuel:
    • If a test fails with fuel exhausted, set solve_fuel on the test entry in the manifest.
  • Runner traps:
    • When a test runner traps, the report includes diagnostic X07T_RUN_TRAP with details.trap set to the decoded trap string.
  • Progress output:
    • x07 test --verbose prints test: <id> lines to stderr while preserving the machine report on stdout.
  • OS-world working directory:
    • For OS worlds (run-os, run-os-sandboxed), the runner process cwd is set from the test manifest directory when possible (sandboxed tests may choose a different cwd to satisfy policy read roots).
    • Relative filesystem paths in test programs are resolved from that cwd (not from the repo root).

Why X07 includes a built-in test harness​

Agents need:

  • a single canonical way to run tests
  • a structured report
  • stable failure semantics

If every project reinvents testing, agents become unreliable.

Toolchain unit tests (Rust)​

When changing compiler/toolchain internals, run:

  • cargo test -p x07c

For minimal repro tests, add a grep-friendly tag:

  • REGRESSION: <id> (for example REGRESSION: x07.rfc.backlog.unit-tests@0.1.0)

To find regression tests:

  • rg "REGRESSION:" crates/x07c

Compiler fuzzing (CI smoke gate)​

The toolchain repo includes cargo-fuzz targets under labs/fuzz/. CI runs a short fuzz smoke gate (30 seconds per target) and uploads labs/fuzz/artifacts/ on failure to enable local reproduction.

To run locally:

  • cargo install cargo-fuzz
  • cargo +nightly fuzz run --fuzz-dir labs/fuzz parse_x07ast_json -- -max_total_time=30
  • cargo +nightly fuzz run --fuzz-dir labs/fuzz parse_sexpr -- -max_total_time=30
  • cargo +nightly fuzz run --fuzz-dir labs/fuzz compile_program_to_c -- -max_total_time=30

To reproduce a CI crash input:

  • cargo +nightly fuzz run --fuzz-dir labs/fuzz <target> labs/fuzz/artifacts/<target>/crash-*