Suitcase
The structured test toolkit. A lightweight sync Rust library for named cases, optional setup / teardown at suite scope and before_each / after_each around each case. Build case lists with cases!; use test_suite! so each case appears as its own line in cargo test, with all those tests sharing one suite behind a Mutex.
Heavy development: The API is still evolving. Expect breaking changes between releases until a stable 1.0; pin an exact version (or git revision) in Cargo.toml if you need upgrades to be predictable.
Install · Usage · Assertions · Mocking · Examples · AI-assisted changes · Docs (after publish; cargo doc --open locally)
- Sync runner —
runorchestrates hooks and case bodies; integrate async I/O with something liketokio::runtime::Handle::block_onin hooks or cases. - Hooks as optional fns —
HookFnsholdsOption<fn(&mut S)>per lifecycle slot; use [None] to skip. - Macros —
cases!builds&'static [Case<S>].test_suite!emits one#[test]per case name; each run usesRunConfig::filterand the same shared suite (see macro docs forSendand ordering). - Assertions —
suitecase::assertprovides testify/assert-style helpers (equal,contains,assert_ok, …) that panic on failure with clear messages (#[track_caller]where applicable). - Mocking —
suitecase::mockprovides testify/mock-style expectations and call recording (Mock,mock_args!). Usesuitecase::mock_argsat the crate root (same macro).
Install
Add suitecase to your Cargo.toml (no required dependencies beyond std):
[]
= "0.1"
Usage
Quickstart
Put this in tests/suite.rs or #[cfg(test)] mod tests { ... }. The example is cargo test --example quickstart — one test line that runs every case in order on one suite.
use ;
static MY_CASES: & = cases!;
static MY_HOOKS: = HookFns ;
Run: cargo test.
Hooks
Pass HookFns as the last argument to run. Each field is Option<fn(&mut S)> — [Some(...)] or [None] / [HookFns::default()].
One line per case in cargo test (test_suite!)
test_suite! expands to one #[test] per listed case. Each test locks a shared Mutex<S> (keyed by a static name you choose), then calls [run] with [RunConfig::filter] for that case. Later tests can observe mutations from earlier runs on the same suite value.
use ;
// MY_CASES, MY_HOOKS, Counter …
test_suite!;
Run: cargo test. See the macro’s rustdoc for ordering (parallel harness) vs a single run with RunConfig::all.
Assertions (assert)
Import helpers from suitecase::assert inside #[test] functions, suite case bodies, or anywhere you want a named check that fails by panicking with a readable message.
use ;
let n = assert_ok;
equal;
contains_str;
See the module docs for the full flat list (collections, errors, floats, options/results, ordering, panics, pointers, time, …).
Mocking (mock)
suitecase::mock is for test doubles: register expectations on a Mock, forward calls from your stub with method_called and mock_args!, then verify with assert_expectations and a small TestingT implementation.
use ;
;
let m = new;
m.on
.returning
.finish;
let out = m.method_called;
assert_eq!;
assert!;
Unexpected calls panic from method_called (see rustdoc). Matchers include eq, anything, anything_of_type, matched_by.
Examples
| Example | Run |
|---|---|
examples/quickstart.rs |
cargo test --example quickstart |
examples/mock.rs |
cargo run --example mock · cargo test --example mock (mocked HTTP-style JSON) |
examples/sqlx_sqlite.rs |
cargo test --example sqlx_sqlite |
| Every example at once | cargo test --examples |
Integration tests (tests/suite.rs) |
cargo test |
The sqlx example uses sqlx + tokio, embedded migrations in setup_suite, and cases! blocks that call helper functions, plus test_suite!.
[]
= "0.1"
= { = "0.8", = ["runtime-tokio", "sqlite", "migrate"] }
= { = "1", = ["macros", "rt-multi-thread"] }
More documentation
AI_USAGE.md— using LLMs to draft changes is allowed; you must understand the patch, justify it in review, and avoid unnecessary complexity (see file).cargo doc --open—cases!andtest_suite!include declaration / description / examples.- Crate root and
suitedescribe howrunselects cases and orders hooks. assert— panicking assertion helpers (submodules per domain; flat re-exports at the module root).mock—Mock, matchers,Arguments,mock_args!.