rust-testing

Rust testing patterns organize unit tests within #[test] modules alongside source code and integration tests in a separate tests directory. This separation ensures components are validated independently before verifying cross-module interactions using cargo test.

Async testing in Rust involves designing tests specifically for asynchronous code using Tokio or async-std. The patterns provide structured workflows to handle futures and async assertions, ensuring reliable validation of concurrent operations.

Property-based testing in Rust explores the input space using proptest to validate robust invariants. Rather than specifying exact values, it automatically generates varied test cases to uncover edge cases that traditional unit tests might miss.

Mocking and isolation in Rust testing simulate dependencies with mocking frameworks to isolate the unit under test. This allows developers to control external behavior and verify component logic independently without relying on actual implementations.

Test coverage and quality gates in Rust establish coverage targets and CI checks to ensure code quality. By integrating these checks into continuous integration pipelines, teams enforce testing standards and prevent untested code from merging.

The TDD workflow for Rust involves identifying test targets, writing failing tests first, then implementing code to pass them. This Skill generates a complete suite skeleton covering unit, integration, async, and property-based tests aligned with TDD principles.