Writing Unit Tests
In this page:
Marking a Function as a Test
The #[test] attribute tells Cargo's test runner that a function is a test case, which it will execute and report the result of when you run cargo test.
Example: Marking a Function as a Test
fn add(a: i32, b: i32) -> i32 {
a + b
}
#[test]
fn test_add() {
assert_eq!(add(2, 3), 5);
}
fn main() {
println!("add(2, 3) = {}", add(2, 3));
}Login to try C/C++/Java/PHP code in the editor
Organizing Tests in a Module
Convention places unit tests in a nested module annotated with #[cfg(test)], so the test code is compiled only when running tests, not included in regular release builds.
Example: Organizing Tests in a Module
fn multiply(a: i32, b: i32) -> i32 {
a * b
}
#[cfg(test)]
mod tests {
use super::*;
#[test]
fn test_multiply() {
assert_eq!(multiply(3, 4), 12);
}
}
fn main() {
println!("multiply(3, 4) = {}", multiply(3, 4));
}Login to try C/C++/Java/PHP code in the editor
Running Tests with cargo test
cargo test compiles the project in test mode, discovers every function marked #[test], runs them all, and prints a pass/fail summary.
Example: Running Tests with cargo test
cargo test⚠️ Run this command in your terminal.
Testing Multiple Cases
A function is often exercised by several test cases covering typical inputs, edge cases, and boundary conditions, each as its own #[test] function.
Example: Testing Multiple Cases
fn is_even(n: i32) -> bool {
n % 2 == 0
}
#[test]
fn test_even_number() {
assert!(is_even(4));
}
#[test]
fn test_odd_number() {
assert!(!is_even(7));
}
fn main() {
println!("is_even(4) = {}", is_even(4));
println!("is_even(7) = {}", is_even(7));
}Login to try C/C++/Java/PHP code in the editor
- Forgetting the
#[test]attribute above a test function, which meanscargo testwill not recognize or run it. - Writing test functions outside of a
#[cfg(test)]module, causing them to be compiled into the regular release binary unnecessarily. - Testing implementation details that change often instead of testing the public, stable behavior of a function.
#[test]marks a function as a test thatcargo testwill discover and run.- Tests are conventionally placed inside a
#[cfg(test)] mod tests { ... }block, keeping them separate from release builds. assert_eq!,assert!, andassert_ne!are the primary macros used to check expected outcomes inside tests.cargo testcompiles and runs every discovered test, reporting pass/fail results for each.
Chapter Quiz — Complete all 8 topics to unlock
0/8 topics done
Complete these topics first: