Why doesn’t println! work in Rust unit tests?

by

This happens because Rust test programs hide the stdout of successful tests in order for the test output to be tidy. You can disable this behavior by passing the --nocapture option to the test binary or to cargo test (but, in this case after -- – see below):

#[test]
fn test() {
    println!("Hidden output")
}

Invoking tests:

% rustc --test main.rs; ./main

running 1 test
test test ... ok

test result: ok. 1 passed; 0 failed; 0 ignored; 0 measured

% ./main --nocapture

running 1 test
Hidden output
test test ... ok

test result: ok. 1 passed; 0 failed; 0 ignored; 0 measured

% cargo test -- --nocapture

running 1 test
Hidden output
test test ... ok

test result: ok. 1 passed; 0 failed; 0 ignored; 0 measured

If tests fail, however, their stdout will be printed regardless if this option is present or not.

More Related Contents:

  1. How to print a Vec?
  2. What is the difference between iter and into_iter?
  3. How can I swap in a new value for a field in a mutable reference to a structure?
  4. How does for syntax differ from a regular lifetime bound?
  5. Why is this match pattern unreachable when using non-literal patterns?
  6. How to convert a String into a &’static str
  7. Proper way to return a new string in Rust
  8. Double mutable borrow error in a loop happens even with NLL on
  9. How to return a reference to a sub-value of a value that is under a mutex?
  10. Is it possible to make a type only movable and not copyable?
  11. How can this instance seemingly outlive its own parameter lifetime?
  12. How to use struct self in member method closure
  13. How do I call a function through a member variable?
  14. How do you pass a Rust function as a parameter?
  15. Why does removing return give me an error: expected type `()` but found type
  16. How do I implement a trait with a generic method?
  17. cannot borrow `self.x` as immutable because `*self` is also borrowed as mutable
  18. Using the same iterator multiple times in Rust
  19. How do I fix “cannot find derive macro in this scope”?
  20. Thread ” has overflowed its stack when allocating a large array using Box
  21. Why is the bound `T: ‘a` required in order to store a reference `&’a T`?
  22. How can a Rust program access metadata from its Cargo package?
  23. How can the ref keyword be avoided when pattern matching in a function taking &self or &mut self?
  24. How do I disambiguate traits in Rust?
  25. Expected bound lifetime parameter, found concrete lifetime [E0271]
  26. How do I change a function’s qualifiers via conditional compilation?
  27. How to quiet a warning for a single statement in Rust?
  28. Is there an elegant solution to modifying a structure while iterating?
  29. Can a struct containing a raw pointer implement Send and be FFI safe?
  30. Lazy sequence generation in Rust

Leave a Comment