Test runner should pick up environment variables from launchSettings.json

[Eilon]

This has been reported a couple of times in other repos:

• Integration tests and Startup.cs / appsettings.json Mvc#4230
• Environment variables are not available during unit test execution. Testing#202

And it seems like it would be quite useful, as environment variables are important for a lot of code to run correctly, and thus important in testing scenarios.

cc @vijayrkn @BillHiebert

[sayedihashimi]

TFS: 219219
I've added this to our internal TFS, we will reply back here soon.

[gzak]

@sayedihashimi any updates?

[barrytang]

We won't be fixing this for VS2015 and the next version of VS will have a different experience.

[senwen]

Just got bit by this. @barrytang, what do you suggest as the workaround for VS2015? Our team relies on unit tests working properly as part of our CI/CD process and the idea of hard coding environment values in our unit tests or loading and managing environment values from another source is not ideal.

[arielcloud]

Is it fixed on VS 2017? how can I use environment variables on integration tests? thanks!

[sthomas1978]

I have exactly the same problem. Dont know whether this helps but when I create a a test server I do the following

var config = new ConfigurationBuilder()
.AddCommandLine(new[] {"--environment=Development"})
.Build();

var server = new TestServer(new WebHostBuilder()
.UseConfiguration(config)
.UseStartup<Startup>());

This lets me inject the environment I am using via the command line. It seems to work for me

[eswann]

Is this fixed? The test framework isn't picking up environment variables for me. This should be reopened. I am using VS 2017 pro.

[justin-lavelle]

Also for me this does not seem to be working.

Microsoft Visual Studio Professional 2017
Version 15.2 (26430.4) Release

The environment variables in launchSettings.json are not available in the EnvironmentVariablesConfigurationProvider .

[edward93]

@sthomas1978 your solution didn't work for me. I suspect via --environment parameter you cannot pass your env var anymore

[richturner]

Why is this issue (and duplicates) closed?

This is a fundamental problem that setting the environment variables in a test project should be available in the tests, only thing for this at the moment seems to be to parse the launchSettings.json file and pass the environment variables into the ConfigurationBuilder