How common is TDD (test-first) in real-world Rust projects?

116 points Strong-Cantaloupe152 197 comments

I’m curious about the role of test-driven development (writing tests before implementation) in the Rust ecosystem.

Coming from a JVM background, I’m used to TDD as a design tool, especially for async and concurrent code. In Rust, I see much more emphasis on:

•	type-driven development,

•	property-based testing,

•	fuzzing,

•	post-factum unit tests.

My questions:

•	Do teams actually practice test-first / TDD in production Rust code?

•	If yes, in which domains (backend systems, infra, libraries, embedded, etc.)?

•	Or is TDD generally seen as redundant given Rust’s type system and compiler guarantees?

I’m not asking whether tests are written (obviously they are), but whether TDD as a workflow is common or intentionally avoided in Rust.

Interested in real-world experiences rather than theory.