nushell/tests/shell/environment/mod.rs

mod configuration;
mod env;
mod in_sync;
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;`
Refactor nu-cli/env* (#3041) * Revert "History, more test coverage improvements, and refactorings. (#3217)" This reverts commit 8fc8fc89aaf0ab40e7a149f2286eb97515f4ac9b. * Add tests * Refactor .nu-env * Change logic of Config write to logic of read() * Fix reload always appends to old vars * Fix reload always takes last_modified of global config * Add reload_config in evaluation context * Reload config after writing to it in cfg set / cfg set_into * Add --no-history to cli options * Use --no-history in tests * Add comment about maybe_print_errors * Get ctrl_exit var from context.global_config * Use context.global_config in command "config" * Add Readme in engine how env vars are now handled * Update docs from autoenv command * Move history_path from engine to nu_data * Move load history out of if * No let before return * Add import for indexmap 2021-03-31 05:52:34 +00:00			`mod env;`
History, more test coverage improvements, and refactorings. (#3217) Improvements overall to Nu. Also among the changes here, we can also be more confident towards incorporating `3041`. End to end tests for checking envs properly exported to externals is not added here (since it's in the other PR) A few things added in this PR (probably forgetting some too) * no writes happen to history during test runs. * environment syncing end to end coverage added. * clean up / refactorings few areas. * testing API for finer control (can write tests passing more than one pipeline) * can pass environment variables in tests that nu will inherit when running. * No longer needed. * no longer under a module. No need to use super. 2021-03-27 05:08:03 +00:00			`mod in_sync;`
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`
			`}`
			`}`
			`}`