test-runner

Rust testing runs three test types via cargo: unit tests with `cargo test --lib`, integration tests with `cargo test --test '*'`, and documentation tests with `cargo test --doc`. Each targets different test files and validates distinct aspects of your crate.

Organize tests by type—unit tests in src files, integration tests in tests/ directory, doc tests in code comments—then run selectively using `cargo test --lib`, `cargo test --test`, or `cargo test --doc` to isolate failures and speed up local feedback loops.

Yes, cargo test supports CI automation with flags like `--nocapture` for output visibility, release-mode builds for performance testing, and environment-variable configuration to ensure reproducible results across local and pipeline environments.

Isolate failures by running specific test modules or single tests, use `--nocapture` to see println output, check for environment-variable dependencies, and run full suites with `--all` to distinguish module-level from integration issues.

Yes, `cargo test --doc` executes code examples in documentation comments and doc attributes, validating that API documentation examples compile and run correctly as part of your test suite.