Some command line options go to cargo test, and some go to the resulting test binary. To separate these two types of arguments, you list the arguments that go to cargo test followed by the separator -- and then the ones that go to the test binary. Running cargo test --help displays the options you can use with cargo test, and running cargo test -- --help displays the options you can use after the separator --.

    When you run multiple tests, by default they run in parallel using threads. This means the tests will finish running faster so you can get feedback quicker on whether or not your code is working. Because the tests are running at the same time, make sure your tests don’t depend on each other or on any shared state, including a shared environment, such as the current working directory or environment variables.

    For example, say each of your tests runs some code that creates a file on disk named test-output.txt and writes some data to that file. Then each test reads the data in that file and asserts that the file contains a particular value, which is different in each test. Because the tests run at the same time, one test might overwrite the file between when another test writes and reads the file. The second test will then fail, not because the code is incorrect but because the tests have interfered with each other while running in parallel. One solution is to make sure each test writes to a different file; another solution is to run the tests one at a time.

    If you don’t want to run the tests in parallel or if you want more fine-grained control over the number of threads used, you can send the --test-threads flag and the number of threads you want to use to the test binary. Take a look at the following example:

    We set the number of test threads to 1, telling the program not to use any parallelism. Running the tests using one thread will take longer than running them in parallel, but the tests won’t interfere with each other if they share state.

    By default, if a test passes, Rust’s test library captures anything printed to standard output. For example, if we call println! in a test and the test passes, we won’t see the println! output in the terminal; we’ll see only the line that indicates the test passed. If a test fails, we’ll see whatever was printed to standard output with the rest of the failure message.

    As an example, Listing 11-10 has a silly function that prints the value of its parameter and returns 10, as well as a test that passes and a test that fails.

    Filename: src/lib.rs

    1. fn prints_and_returns_10(a: i32) -> i32 {
    2.     println!("I got the value {}", a);
    3.     10
    4. }
    6. #[cfg(test)]
    7. mod tests {
    8.     use super::*;
    10.     #[test]
    11.     fn this_test_will_pass() {
    12.         let value = prints_and_returns_10(4);
    13.         assert_eq!(10, value);
    14.     }
    16.     #[test]
    17.     fn this_test_will_fail() {
    18.         let value = prints_and_returns_10(8);
    19.         assert_eq!(5, value);
    20.     }
    21. }

    When we run these tests with cargo test, we’ll see the following output:

    1. $ cargo test
    2.    Compiling silly-function v0.1.0 (file:///projects/silly-function)
    3.     Finished test [unoptimized + debuginfo] target(s) in 0.58s
    4.      Running unittests (target/debug/deps/silly_function-160869f38cff9166)
    6. running 2 tests
    7. test tests::this_test_will_fail ... FAILED
    8. test tests::this_test_will_pass ... ok
    10. failures:
    12. ---- tests::this_test_will_fail stdout ----
    13. I got the value 8
    14. thread 'main' panicked at 'assertion failed: `(left == right)`
    15.   left: `5`,
    16.  right: `10`', src/lib.rs:19:9
    17. note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
    20. failures:
    24. error: test failed, to rerun pass '--lib'

    Note that nowhere in this output do we see I got the value 4, which is what is printed when the test that passes runs. That output has been captured. The output from the test that failed, I got the value 8, appears in the section of the test summary output, which also shows the cause of the test failure.

    If we want to see printed values for passing tests as well, we can tell Rust to also show the output of successful tests at the end with --show-output.

    1. $ cargo test -- --show-output

    When we run the tests in Listing 11-10 again with the --show-output flag, we see the following output:

    Sometimes, running a full test suite can take a long time. If you’re working on code in a particular area, you might want to run only the tests pertaining to that code. You can choose which tests to run by passing cargo test the name or names of the test(s) you want to run as an argument.

    To demonstrate how to run a subset of tests, we’ll create three tests for our add_two function, as shown in Listing 11-11, and choose which ones to run.

    Filename: src/lib.rs

    1. pub fn add_two(a: i32) -> i32 {
    2.     a + 2
    3. }
    5. #[cfg(test)]
    6. mod tests {
    7.     use super::*;
    9.     #[test]
    10.     fn add_two_and_two() {
    11.         assert_eq!(4, add_two(2));
    12.     }
    14.     #[test]
    15.     fn add_three_and_two() {
    16.         assert_eq!(5, add_two(3));
    17.     }
    19.     #[test]
    20.     fn one_hundred() {
    21.         assert_eq!(102, add_two(100));
    22.     }
    23. }

    Listing 11-11: Three tests with three different names

    1. $ cargo test
    2.    Compiling adder v0.1.0 (file:///projects/adder)
    3.     Finished test [unoptimized + debuginfo] target(s) in 0.62s
    4.      Running unittests (target/debug/deps/adder-92948b65e88960b4)
    6. running 3 tests
    7. test tests::add_three_and_two ... ok
    8. test tests::add_two_and_two ... ok
    9. test tests::one_hundred ... ok
    11. test result: ok. 3 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s
    13.    Doc-tests adder
    15. running 0 tests
    17. test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s

    Running Single Tests

    We can pass the name of any test function to cargo test to run only that test:

    1. $ cargo test one_hundred
    2.    Compiling adder v0.1.0 (file:///projects/adder)
    3.      Running unittests (target/debug/deps/adder-92948b65e88960b4)
    5. running 1 test
    6. test tests::one_hundred ... ok
    8. test result: ok. 1 passed; 0 failed; 0 ignored; 0 measured; 2 filtered out; finished in 0.00s

    Only the test with the name ran; the other two tests didn’t match that name. The test output lets us know we had more tests than what this command ran by displaying 2 filtered out at the end of the summary line.

    We can’t specify the names of multiple tests in this way; only the first value given to cargo test will be used. But there is a way to run multiple tests.

    Filtering to Run Multiple Tests

    We can specify part of a test name, and any test whose name matches that value will be run. For example, because two of our tests’ names contain add, we can run those two by running cargo test add:

    This command ran all tests with add in the name and filtered out the test named one_hundred. Also note that the module in which a test appears becomes part of the test’s name, so we can run all the tests in a module by filtering on the module’s name.

    Sometimes a few specific tests can be very time-consuming to execute, so you might want to exclude them during most runs of cargo test. Rather than listing as arguments all tests you do want to run, you can instead annotate the time-consuming tests using the ignore attribute to exclude them, as shown here:

    Filename: src/lib.rs

    1. #[test]
    2. fn it_works() {
    3.     assert_eq!(2 + 2, 4);
    4. }
    6. #[test]
    7. #[ignore]
    8. fn expensive_test() {
    9.     // code that takes an hour to run
    10. }

    After #[test] we add the #[ignore] line to the test we want to exclude. Now when we run our tests, it_works runs, but expensive_test doesn’t:

    1. $ cargo test
    2.    Compiling adder v0.1.0 (file:///projects/adder)
    3.     Finished test [unoptimized + debuginfo] target(s) in 0.60s
    4.      Running unittests (target/debug/deps/adder-92948b65e88960b4)
    6. running 2 tests
    7. test expensive_test ... ignored
    8. test it_works ... ok
    10. test result: ok. 1 passed; 0 failed; 1 ignored; 0 measured; 0 filtered out; finished in 0.00s
    12.    Doc-tests adder
    14. running 0 tests
    16. test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s
    1. $ cargo test -- --ignored
    2.    Compiling adder v0.1.0 (file:///projects/adder)
    3.     Finished test [unoptimized + debuginfo] target(s) in 0.61s
    4.      Running unittests (target/debug/deps/adder-92948b65e88960b4)
    6. running 1 test
    7. test expensive_test ... ok
    9. test result: ok. 1 passed; 0 failed; 0 ignored; 0 measured; 1 filtered out; finished in 0.00s
    11.    Doc-tests adder
    13. running 0 tests
    15. test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s

    By controlling which tests run, you can make sure your cargo test results will be fast. When you’re at a point where it makes sense to check the results of the ignored tests and you have time to wait for the results, you can run cargo test -- --ignored instead.