test test::send_sample_messages

[Geert Stappers]

Hello,

Sharing this with you all

stappers@messer:~/src/github/mailcrab/backend
$ cargo test send_sample_messages -- --ignored
    Finished test [unoptimized + debuginfo] target(s) in 0.06s
     Running unittests src/main.rs (target/debug/deps/mailcrab_backend-97d1a98261d37e44)

running 1 test
test test::send_sample_messages ... FAILED

failures:

---- test::send_sample_messages stdout ----
thread 'test::send_sample_messages' panicked at 'called `Result::unwrap()` on
 an `Err` value: MissingParts', src/main.rs:366:18
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace


failures:
    test::send_sample_messages

test result: FAILED. 0 passed; 1 failed; 0 ignored; 0 measured; 1 filtered out; finished in 0.09s

error: test failed, to rerun pass `--bin mailcrab-backend`
stappers@messer:~/src/github/mailcrab/backend
$ git checkout coexist 
Switched to branch 'coexist'
stappers@messer:~/src/github/mailcrab/backend
$ cargo test send_sample_messages -- --ignored
   Compiling mailcrab-backend v0.10.0 (/home/stappers/src/github/mailcrab/backend)
    Finished test [unoptimized + debuginfo] target(s) in 1.80s
     Running unittests src/main.rs (target/debug/deps/mailcrab_backend-97d1a98261d37e44)

running 1 test
test test::send_sample_messages ... ok

test result: ok. 1 passed; 0 failed; 0 ignored; 0 measured; 1 filtered out; finished in 0.19s

stappers@messer:~/src/github/mailcrab/backend
$ cargo test send_sample_messages -- --ignored
    Finished test [unoptimized + debuginfo] target(s) in 0.06s
     Running unittests src/main.rs (target/debug/deps/mailcrab_backend-97d1a98261d37e44)

running 1 test
test test::send_sample_messages ... ok

test result: ok. 1 passed; 0 failed; 0 ignored; 0 measured; 1 filtered out; finished in 0.20s

stappers@messer:~/src/github/mailcrab/backend
$ 

It says:

• When I do cargo test send_sample_messages -- --ignored I get a completely useless error.
• When executing that same command in branch coexist I get ok.

This issue should make explaining an upcoming merge request easy.