CamCraft

Developers

Test gates

Tests run locally, on any OS, through one command from the workspace's xtask/ crate: cargo xtask gate <tier>. There are three tiers, so a change is never held up by hours of unrelated tests.

TierWhenWhat it runsTarget
quickevery changeonly the test binaries and test functions the diff touches, in debug5 minutes or less
batchbefore a batch of commitsevery debug suite except the slow ones, the UI suites, and clippy20 minutes or less
releaseat a release cuteverything, including the ignored heavy lanes in release modeas long as it takes
cargo xtask gate quick                 # what this branch touches, against main
cargo xtask gate quick --base main     # name the base explicitly
cargo xtask gate batch
cargo xtask gate release
cargo xtask gate test <name> [--crate c] [--exact]   # one test
cargo xtask gate quick --dry-run       # print the plan, run nothing

Logs go to gate-logs/<tier>-<timestamp>/. The scripts scripts/gate.ps1 (PowerShell) and scripts/gate.sh (bash) are thin wrappers that forward to cargo xtask gate. The cargo xtask gate command itself is the same on Windows, macOS and Linux.

Test the change, not everything

A fix is proved by the tests that pin it, run one by one. A whole suite runs only when the change touches what that suite covers; each suite's header names the modules it covers (its gate map), and quick picks suites from those maps.

Where tests live

GitHub Actions

Nothing runs on push or pull request: Actions minutes are budgeted. GitHub runs only release.yml, on a pushed release tag, to build and publish the release (and this site).