#test #tokio #run-time #shared #test-cases

dev tokio-shared-rt

Allow #[tokio::test] to use a shared runtime

1 unstable release

0.1.0 May 26, 2023

#384 in Testing

Download history 273/week @ 2024-03-13 287/week @ 2024-03-20 401/week @ 2024-03-27 481/week @ 2024-04-03 695/week @ 2024-04-10 430/week @ 2024-04-17 482/week @ 2024-04-24 335/week @ 2024-05-01 495/week @ 2024-05-08 416/week @ 2024-05-15 388/week @ 2024-05-22 336/week @ 2024-05-29 258/week @ 2024-06-05 451/week @ 2024-06-12 356/week @ 2024-06-19 357/week @ 2024-06-26

1,510 downloads per month
Used in 6 crates

MIT license

8KB
73 lines

tokio-shared-rt

Allow #[tokio::test] to use a shared runtime, so that static variables that connect to a tokio runtime inside are still valid between different test cases.

For example, if you have a global, static database connection pool, it internally holds references to some TCP connections which are bound to the runtime that created it. So if you have two test cases that are both marked #[tokio::test] and access that db pool, good chance is that one of them will fail.

thread 't3' panicked at 'called Result::unwrap() on an Err value: Custom { kind: Other, error: "A Tokio 1.x context was found, but it is being shutdown." }'

This crate provides a macro that uses a shared tokio runtime to run test cases to avoid this problem. Just replace your #[tokio::test] with #[tokio_shared_rt::test(shared)] and vualá! Now test passes.

Usage

#[tokio_shared_rt::test]
async fn t1() {
    db_pool().foo().await;
}
#[tokio_shared_rt::test(shared)]
async fn t2() {
    db_pool().foo().await;
}
#[tokio_shared_rt::test(shared = true)]
async fn t3() {
    db_pool().foo().await;
}
#[tokio_shared_rt::test(shared = false)]
async fn delicate_runtime_test() {
    db_pool().foo().await;
}

Dependencies

~2.3–4MB
~65K SLoC