How to set environment variables for test?

[feslima]

When using vim-ultest I could use the ultest_env variable to set my environment variables for the test suite. I've tried digging around the project docs/source but couldn't find where I could do this here.

Is is possible to achieve this feature with neotest? If so, how?

Thanks in advance!

[rcarriga]

I hadn't actually allowed this using the run API but I've now added an env argument to the args table to supplement the environment 😄

[rcarriga]

Ah so this is not currently possible without users changing their config due to the behaviour of nvim-dap. I've opened an issue to see if that can change mfussenegger/nvim-dap#587

[feslima]

Nevermind! I can simply pass the env table as to the adapter itself. It works now.

For anyone wondering how to do this, in the neotest-python config, pass your env table to the dap arg:

neotest.setup({
  ...
  require('neotest-python')({
    dap = { env = your_env_table },
    ...
  }),
  ...
})

[feslima]

Indeed, I do agree that passing the env per run options is less complex to config.

Thank you anyway.

[rcarriga]

Good to know that works 👍 As far as I know that's dependent on the adapter accepting the env argument so that works for debugpy but not necessarily for others

[jetaggart]

How would you do this for neotest-go? Sorry, this isn't super clear to me how we can set env vars per adapter.

[feslima]

@rcarriga Hey, it's me again! Quick question: the setup using neotest.run.run({ env=my_env_table }) was changed? It's been a while since my last package update and, when I did update yesterday, it appears that neotest.run.run({ env=my_env_table }) is ignoring the env table I set and sends nothing to the runner. Is there any procedure where I can debug this?

[feslima]

I've tried some crude debugging to see what values spec is receiving after this line.

This is the spec value:

The env table set in args isn't set on spec. Is this intended to be like this?

[feslima]

I was able to make it work again using this:

if args.env then
  spec.env = args.env
end

after this line.

Hope it helps!

[jonatan-branting]

Shouldn't the adapter handle that? It receives args through build_spec on line 28 in your example.

Although support for env variables without explicit adapter support maybe isn't the worst idea, either.

[feslima]

@jonatan-branting I've tested earlier, this isn't working too. Since there no changes in the docs about the env being set on the runner, I thought this is still supported, even though he mentioned that its support is dependent on adapter and this PR was closed without changes.

For now, this dirty "fix" is working

[rcarriga]

Hmm thought I replied to this but apparently not 🤦 I fixed this a couple of days ago, you should see env vars working again!