use-test is the RustUse facade/set for primitive testing vocabulary. RustUse is a collection of composable, dependency-light Rust utility crates, and this workspace provides small metadata types for assertions, expectations, test cases, suites, outcomes, statuses, fixtures, snapshots, and lightweight reports.

This repository is experimental while it is below 0.3.0. APIs are intentionally small and may change as the RustUse testing vocabulary settles.

use-test is a primitive vocabulary layer for projects that need to describe testing concepts without adopting a runner, framework, mocking system, snapshot engine, or CI integration.

• Primitive Rust testing metadata types.
• Focused child crates with small public APIs.
• A facade crate that exposes child crates through module-style aliases.
• A shared vocabulary for assertions, expectations, cases, suites, outcomes, statuses, fixtures, snapshots, and reports.

• Not a test runner.
• Not a test framework.
• Not a replacement for Rust's built-in test system.
• Not a replacement for crates like proptest, rstest, insta, or criterion.
• Not a mocking, fake, stub, or spy framework.
• Not a snapshot file storage engine.
• Not a benchmark framework.
• Not a CI system or reporting integration.

All child crates in this workspace use the use-test-* naming pattern. This keeps testing-specific primitives from colliding with broader RustUse vocabulary crates while making their relationship to the use-test facade explicit.

[dependencies]
use-test = "0.1.0"

Focused crates can also be used directly:

[dependencies]
use-test-case = "0.1.0"
use-test-outcome = "0.1.0"

use use_test::case::TestCase;
use use_test::expectation::TestExpectation;
use use_test::outcome::TestOutcome;

let case = TestCase::new("empty string trims to empty");
let expectation = TestExpectation::new("", "".trim());
let outcome = TestOutcome::Passed;

assert_eq!(case.name(), "empty string trims to empty");
assert_eq!(expectation.expected(), expectation.actual());
assert!(outcome.is_success());

• Assertion, expectation, test case, and test suite metadata.
• Outcome and lifecycle status vocabulary.
• Fixture scope metadata.
• Snapshot identity/version/status labels without file I/O.
• Lightweight summary counts and success-rate helpers.

• Running tests, scheduling tests, discovering tests, or integrating with test harnesses.
• Assertion macros, procedural macros, property testing, fuzzing, or benchmark execution.
• Mocking, spying, fake services, dependency injection, or fixture setup/teardown execution.
• Snapshot file storage, golden-file updates, or snapshot review commands.
• External report formats such as JUnit XML in v0.1.0.

cargo fmt --all -- --check
cargo clippy --workspace --all-targets --all-features -- -D warnings
cargo test --workspace --all-features

For release-readiness checks, also run the repository tasks in the Makefile.

Licensed under either of the following, at your option:

• Apache License, Version 2.0
• MIT license