Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow envFile alternative to env in java.test.config #1214

Closed
nerdkid93 opened this issue Jun 18, 2021 · 2 comments · Fixed by #1326
Closed

Allow envFile alternative to env in java.test.config #1214

nerdkid93 opened this issue Jun 18, 2021 · 2 comments · Fixed by #1326

Comments

@nerdkid93
Copy link

The VS Code launch.json file allows specifying envFile in addition to env. However, there does not appear to be a similar mechanism when running tests via this extension. It would be super handy to be able to have 1 file specify the env rather than duplicate it in both .env and .vscode/settings.json.

@jdneo
Copy link
Member

jdneo commented Nov 2, 2021

The next release will happen around the end of Nov.

@jdneo
Copy link
Member

jdneo commented Nov 22, 2021

End game verification steps:

  1. Add an .env file in project
  2. Add envFile in java.test.config
  3. Write a test case to verify the .env file is picked:
assertEquals("value", System.getenv("key"));

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants