Testing

Sipp tests are cataloged by cargo xtask test list. Use that command first when choosing a target or checking what CI runs.

Commands

cargo xtask test has four top-level actions:

• list: list unit and smoke suites and optionally discover/search cheap cases.
• unit: run deterministic code-flow and API-layer tests by suite or group.
• smoke: run holistic integration smoke tests by suite or group.
• verify: analyze existing coverage artifacts and validate test structure.

Common Commands

cargo xtask test list
cargo xtask test list --group unit --layer interface --cases --search router --format json
cargo xtask test unit group full
cargo xtask test unit group whitebox
cargo xtask test unit group interface
cargo xtask test unit suite xtask
cargo xtask test unit suite rust-crates --package sipp-rs
cargo xtask test unit suite browser --wasm-threading pthread
cargo xtask test unit suite demos --wasm-threading pthread
cargo xtask test unit suite node-package --backend cpu
cargo xtask test unit suite python-package --backend cpu
cargo xtask test smoke suite example-node --backend cpu
cargo xtask test smoke suite example-gateway --backend cpu --case query
cargo xtask test smoke suite playground-browser
cargo xtask test smoke group examples --backend cpu
cargo xtask test smoke group local-model --backend cpu
cargo xtask test smoke group full --backend cpu
cargo xtask test verify --target whitebox
cargo xtask test verify --changed

test unit owns deterministic tests. It is split into explicit namespaces:

• test unit suite <name> runs exactly one deterministic unit suite.
• test unit group <name> runs a named bundle of deterministic unit suites.

Unit suite names expose suite-specific options, such as test unit suite rust-crates --package <crate> and test unit suite node-package --backend cpu.

Unit Suites

Unit Groups

Browser and demo unit suites accept --wasm-threading single-thread|pthread|all for explicit compatibility testing. The default is pthread, matching the bundled browser package. Release package builds use cargo xtask build wasm, which stages the pthread WebGPU+JSPI and pthread CPU non-JSPI artifacts.

test smoke owns holistic integration checks. It is split into explicit namespaces:

• test smoke suite <name> runs exactly one smoke suite.
• test smoke group <name> runs a named bundle of smoke suites.

Model-backed smoke suites default to the setup sample model cache under .build/models when --model is omitted. Rust, Node, Python, gateway, and browser example smoke accept repeated --case query|chat|embed. Embedding cases require a model/runtime that reports embedding support.

Smoke Suites

Smoke Groups

Use cargo xtask run examples serve browser to manually serve browser examples. Use cargo xtask run examples serve gateway-local --model <model.gguf> to serve the minimal local gateway proxy. Provider-backed and production serving use apps/gateway-server; validate its configuration with sipp run gateway-server check --config <path> and use raw Docker commands from Gateway Docker for container testing. Use Gateway Testing for curl and Postman checks. Playground validation remains under test smoke suite playground-browser.

test unit and test smoke print a final suite and test/check summary, then write .build/test/run-report.json and .build/test/run-report.md. Coverage-capable unit suites also write fresh coverage artifacts under .build/coverage/.

test verify does not execute test suites. It validates test structure, catalog ownership, test/runtime code separation, optional changed-file coverage, and existing coverage artifacts.

Package Locations

• lib/web publishes @noumena-labs/sipp and public @sipphq/sipp.
• lib/node publishes @noumena-labs/sipp-server and public @sipphq/sipp-server.
• lib/python publishes Python sipp.
• crates/sipp publishes the Rust package sipp-rs with library crate sipp.