rust-testing

Topics in the source

• Rust Testing Patterns
• When to Use
• How It Works
• TDD Workflow for Rust
• The RED-GREEN-REFACTOR Cycle
• Step-by-Step TDD in Rust
• Unit Tests
• Module-Level Test Organization

Comprehensive Rust testing patterns for writing reliable, maintainable tests following TDD methodology. Writing new Rust functions, methods, or traits Adding test coverage to existing code Creating benchmarks for performance-critical code Implementing property-based tests for input validation Following TDD workflow in Rust projects 1. Identify target code — Find the function, trait, or module to test 2. Write a test — Use #[test] in a #[cfg(test)] module, rstest for parameterized tests, or proptest for property-based tests 3. Mock dependencies — Use mockall to isolate the unit under test 4. Run tests (RED) — Verify the test fails with the expected error 5. Implement (GREEN) — Write minimal code to pass 6. Refactor — Improve while keeping tests green 7. Check coverage — Use cargo-llvm-cov, target 80%+ | Code Type | Target | |-----------|--------| | Critical business logic | 100% | | Public API | 90%+ | | General code | 80%+ | | Generated / FFI bindings | Exclude | DO: Write tests FIRST (TDD) Use #[cfg(test)] modules for unit tests Test behavior, not implementation Use descriptive test names that explain the scenario Prefer asserteq! over assert! for better error messages Use ? in te

This is an excerpt. Refer to the complete source and its current requirements.