nushell/tests/shell/environment/mod.rs

mod configuration;
mod nu_env;

pub mod support {
    use nu_test_support::{nu, playground::*, Outcome};

    pub struct Trusted;

    impl Trusted {
        pub fn in_path(dirs: &Dirs, block: impl FnOnce() -> Outcome) -> Outcome {
            let for_env_manifest = dirs.test().to_string_lossy();

            nu!(cwd: dirs.root(), format!("autoenv trust \"{}\"", for_env_manifest.to_string()));
            let out = block();
            nu!(cwd: dirs.root(), format!("autoenv untrust \"{}\"", for_env_manifest.to_string()));

            out
        }
    }
}
Playground infraestructure (tests, etc) additions. (#3179) * Playground infraestructure (tests, etc) additions. A few things to note: * Nu can be started with a custom configuration file (`nu --config-file /path/to/sample_config.toml`). Useful for mocking the configuration on test runs. * When given a custom configuration file Nu will save any changes to the file supplied appropiately. * The `$nu.config-path` variable either shows the default configuration file (or the custom one, if given) * We can now run end to end tests with finer grained control (currently, since this is baseline work, standard out) This will allow to check things like exit status, assert the contents with a format, etc) * Remove (for another PR) 2021-03-15 07:26:30 +00:00			`mod configuration;`
Extract .nu-env tests and more granularity (#3078) The autoenv logic mutates environment variables in the running session as it operates and decides what to do for trusted directories containing `.nu-env` files. Few of the ways to interact with it were all in a single test function. We separate out all the ways that were done in the single test function to document it better. This will greatly help once we start refactoring our way out from setting environment variables this way to just setting them to `Scope`. This is part of an on-going effort to keep variables (`PATH` and `ENV`) in our `Scope` and rely on it for everything related to variables. We expect to move away from setting (`std::*`) envrironment variables in the current running process. This is non-trivial since we need to handle cases from vars coming in from the outside world, prioritize, and also compare to the ones we have both stored in memory and in configuration files. Also to send out our in-memory (in `Scope`) variables properly to external programs once we no longer rely on `std::env` vars from the running process. 2021-02-19 01:24:27 +00:00			`mod nu_env;`

			`pub mod support {`
			`use nu_test_support::{nu, playground::*, Outcome};`

			`pub struct Trusted;`

			`impl Trusted {`
			`pub fn in_path(dirs: &Dirs, block: impl FnOnce() -> Outcome) -> Outcome {`
			`let for_env_manifest = dirs.test().to_string_lossy();`

			`nu!(cwd: dirs.root(), format!("autoenv trust \"{}\"", for_env_manifest.to_string()));`
			`let out = block();`
			`nu!(cwd: dirs.root(), format!("autoenv untrust \"{}\"", for_env_manifest.to_string()));`

			`out`
			`}`
			`}`
			`}`