kithara-test-utils

Cross-crate test-runtime support: #[kithara::test] macro re-exports, USDT probe helpers, hang-watchdog, and unimock glue. It carries the test runtime only — the integration-test fixtures themselves (synthetic servers, signal generators, builders) live in kithara-integration-tests. The probe/hang/mock paths are no-ops in release builds, so production code can depend on it normally.

Modules

Usage

use kithara_test_utils::kithara;

#[kithara::test(tokio, timeout(std::time::Duration::from_secs(10)))]
async fn smoke() {
    // test body — protected by the hang watchdog (default-on)
}

For trait mocks:

use kithara_test_utils::kithara;

#[kithara::mock]
trait Service {
    fn get(&self) -> u64;
}

Probe sites compile to no-ops unless kithara-stream/usdt-probes and/or kithara-hls/usdt-probes are enabled in the test build. The capture helper records every probe tracing::event! into a process-wide recorder so a test can snapshot and assert on the full sequence. See CONTEXT.md for the tracing-layer rationale, the process-wide subscriber contract, and the #[serial] requirement.

Features

Consumer crates typically enable mock and probe in their [dev-dependencies] while keeping the default hang feature on.

Integration tests live elsewhere

The integration-test domain (synthetic HLS servers, signal generators, TestHttpServer, TestServerHelper, HlsFixtureBuilder, PackagedTestServer, …) lives in kithara-integration-tests (tests/). To use it from another crate's tests, depend on kithara-integration-tests (it is publish = false) rather than re-implementing fixtures here.

See tests/README.md for the integration-test suite layout, the standalone test_server binary, the WASM flow, and the available fixture builders.

Integration

Consumed by every crate's [dev-dependencies]. The macros it re-exports work on native and wasm32 targets transparently.

See CONTEXT.md for detailed contracts, invariants, and internals.