3 releases

0.1.2 Aug 19, 2024
0.1.1 Aug 15, 2024
0.1.0 Aug 15, 2024

#448 in Concurrency

Download history 20/week @ 2024-10-08 31/week @ 2024-10-15 41/week @ 2024-10-22 28/week @ 2024-10-29 23/week @ 2024-11-05 14/week @ 2024-11-12 28/week @ 2024-11-19 35/week @ 2024-11-26 20/week @ 2024-12-03 55/week @ 2024-12-10 9/week @ 2024-12-17 18/week @ 2024-12-24 325/week @ 2024-12-31 37/week @ 2025-01-07 17/week @ 2025-01-14 13/week @ 2025-01-21

398 downloads per month
Used in 4 crates

MIT license

8KB
92 lines

env-lock

Test CI crates.io docs.rs

A process's environment is a form of global mutable state. In Rust, tests are run in a shared process. This means tests that modify environment variables can inadvertently affect each other. env-lock provides an interface to safely modify and lock the process environment, to prevent simultaneous access.

use std::env;

let var = "ENV_LOCK_TEST_VARIABLE";
assert!(env::var(var).is_err());

let guard = env_lock::lock_env([(var, Some("hello!"))]);
assert_eq!(env::var(var).unwrap(), "hello!");
drop(guard);

assert!(env::var(var).is_err());

lib.rs:

Lock environment variables to prevent simultaneous access. Use [lock_env] to set values for whatever environment variables you intend to access in your test. This will return a guard that, when dropped, will revert the environment to its initial state. The guard uses a [Mutex] underneath to ensure that multiple tests within the same process can't access it at the same time.

use std::env;

let var = "ENV_LOCK_TEST_VARIABLE";
assert!(env::var(var).is_err());

let guard = env_lock::lock_env([(var, Some("hello!"))]);
assert_eq!(env::var(var).unwrap(), "hello!");
drop(guard);

assert!(env::var(var).is_err());

No runtime deps