rust-test-driven-development

Writing failing tests before implementing code in Rust ensures expected behavior is defined upfront. This test-first approach translates acceptance criteria into failing unit and integration tests, followed by minimal implementation and subsequent refactoring.

The Red, Green, Refactor cycle for Rust unit testing involves writing a failing test from acceptance criteria, creating a minimal implementation to pass the test, and refactoring with safety checks. This cycle ensures rigorous test coverage and code quality.

Translate acceptance criteria into failing Rust tests by identifying the current story's SUBTASKS.md and writing test cases that capture the specified expected behavior before any code exists. This ensures the implementation directly matches the required specifications.

Test-driven development works with Rust integration and property-based tests by guiding test-writing patterns with clear naming, fixtures, and test doubles. It applies the same test-first principles across all test types to ensure comprehensive coverage.

For a spec-driven Rust workflow, use testing patterns that include clear naming conventions, structured fixtures, and test doubles aligned to project conventions. These patterns apply across unit, integration, and property-based tests to validate acceptance criteria.

You should avoid a test-first approach for Rust codebase tasks when subtasks lack defined acceptance criteria in STORY.md or SUBTASKS.md. Without clear specifications to translate into failing tests, the structured Red, Green, Refactor cycle cannot be effectively initiated.