Crate temp_env_vars

temp_env_vars

temp_env_vars allows to reset all changes to environment variables changed within the execution of a certain function.

Usage

temp_env_vars can be used in two different forms:

1. as macro #[temp_env_vars]
2. with TempEnvScope::new()

Use as macro

#[temp_env_vars] is the preferred way to use the temp_env_vars crate. Every change to envionrment variables within the execution of the annotated function will be reset after the function has ended.

If more tests are used with this macro, those tests will be executed sequentially to avoid an enviornment variable mixup.

use temp_env_vars::temp_env_vars;

#[test]
#[temp_env_vars]
fn test_some() {
    std::env::set_var("FOO", "BAR");
    assert_eq!(std::env::var("FOO").unwrap(), "BAR");

    // Env vars get reset when this test is done
}

Use with TempEnvScope

If resetting the environment variables after the function execution is not sufficient, but the reset must happen somewhere within the function, the TempEnvScope can be used to have better control.

Whenever the created TempEnvScope goes out of scope, all env vars are reset.

use serial_test::serial;
use temp_env_vars::TempEnvScope;

#[test]
#[serial] // Use external "serial" crate as parallel tests mix up envs
fn test_some() {
    let _env_scope = TempEnvScope::new();
    std::env::set_var("FOO", "BAR");
    assert_eq!(std::env::var("FOO").unwrap(), "BAR");

    // After "_env_scope" goes out of scope, all vars are restored
}

#[test]
#[serial] // Use external "serial" crate as parallel tests mix up envs
fn test_bar() {
    let _env_scope = TempEnvScope::new();
    std::env::set_var("FOO", "BAR");
    assert_eq!(std::env::var("FOO").unwrap(), "BAR");

    drop(_env_scope); // After "_env_scope" goes out of scope, all vars are restored

    // "FOO" is not longer set here.
}

Structs

TempEnvScope

Attribute Macros

temp_env_vars