How to specify separate environment variables file for test vs development

[yawhide]

Howdy,

My development environment has 2 separate env var files:

• .env.dev
• .env.test

I can also override certain env vars by making a:

• .env.dev.local
• .env.test.local

I read through the vscode documentation python environments and python testing and it doesnt seem there is a way to do this natively in vscode.

I cant find a way to say 'testing env file is .env.test, everything else use .env.dev'. i have set "python.envFile": "${workspaceFolder}/.env.dev" in settings.json.

i have been able to also make a launch config to debug tests to use .env.test but I can only debug test cases to make this work. I cant just run test cases.

{
      "name": "Python: Debug Tests",
      "type": "python",
      "request": "launch",
      "program": "${file}",
      "purpose": ["debug-test"],
      "envFile": "${workspaceFolder}/.env.test",
      "console": "integratedTerminal",
      "justMyCode": false
    },

But how do I say 'hey testing, use .env.test'. WHen i run (not debug) test cases, it uses .env.dev :(
Also, I cant find a way for vscode to merge .env.test.local with .env.test either.

any ideas how I can make this work? or do I have to make a feature request?

[eleanorjboyd]

Hi- I think this is what you are looking for, we are planning on implementing this soon and are currently working on a proposal for the design: #21845

[yawhide]

this proposal looks very much on point! i added a comment on the proposal about env var file overriding (.env.test.local can override env vars in .env.test)

[eleanorjboyd]

Great thank you for contributing to the discussion!

[eleanorjboyd]

If this doesn't answer your question please respond and we can reopen this! If you have comments / thoughts on the proposal, feel free to comment directly on the issue. Thanks!