Orion splits validation into default workspace checks, Docker-backed cluster coverage, and longer perf or soak runs.
cargo fmt --check./scripts/check-file-sizes.shcargo clippy --workspace --all-targets --all-features -- -D warningscargo test --workspace --all-featurescargo doc --workspace --no-depscargo audit
The main containerized suites exercise the node and cluster behavior inside testing/docker/orion-node.Dockerfile:
cargo test -p orion-node --test docker_cluster_baseline -- --ignored --nocapturecargo test -p orion-node --test docker_cluster_failure -- --ignored --nocapturecargo test -p orion-node --test docker_cluster_adversarial -- --ignored --nocapturecargo test -p orion-node --test docker_cluster_scale -- --ignored --nocapturecargo test -p orion-node --test docker_client_examples -- --ignored --nocapture
- Perf thresholds and baselines live in
testing/ci/perf-baselines.json - Perf and soak suites stay separate from the default local loop
- Dependency vulnerability checks run in CI with
cargo audit - File-size linting is warning-only, supports
FILE_SIZE_EXCLUDE_DIRS=path1:path2, and tracks current exceptions throughtesting/ci/file-size-baseline.txt