env_wrapper

Build

A wrapper around the standard std::env functions that allows for a test double to be injected during testing.

Limitations

At this time, this crate only works for Unix-like systems.

Motivation

Testing code that relies on the state of environment variables can be fragile, since the state may change between tests or be polluted by other tests. The ideal solution is to have a private set of environment variables per test, so these problems cannot happen.

Approach

This crate introduces the RealEnvironment (a wrapper around the functions in std::env) and FakeEnvironment structs, which implement the Environment trait. Instead of using std::env directly, use RealEnvironment with dependency injection so each of your tests can have a private set of environment variables.

Example

Scenario: An app looks for the presence of the CONFIG_LOCATION environment variable. If it isn't set, it uses a default location.

```rust use env_wrapper::{Environment, RealEnvironment};

const CONFIGLOCATIONENVVARNAME: &str = "CONFIGLOCATION"; const DEFAULTCONFIGLOCATION: &str = "/etc/myapp/service.conf";

fn main() { // In the production code, inject RealEnvironment. let realenv = RealEnvironment; let configlocation = getconfiglocation(real_env); }

fn getconfiglocation(env: impl Environment) -> String { match env.var(CONFIGLOCATIONENVVARNAME) { Ok(location) => location, _ => DEFAULTCONFIGLOCATION.to_string(), } }

[test]

fn whentheuserhassettheconfiglocationenvvarthenusethatlocation() { use envwrapper::FakeEnvironment;

// Arrange
// Each test should have a separate instance of FakeEnvironment.
let mut fake_env = FakeEnvironment::new();
let user_specified_location = "/a/user/specified/location";
fake_env.set_var(CONFIG_LOCATION_ENV_VAR_NAME, user_specified_location);

// Act
// In the test code, inject FakeEnvironment.
let location = get_config_location(fake_env);

// Assert
assert_eq!(location, user_specified_location);

} ```

License

Licensed under either of

at your option.

Contribution

Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in the work by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.

Code of Conduct

All behavior is governed by the Rust Code of Conduct.