feat: support codeLens.testEnvs

[ahuigo]

For #661

This new new option codeLens.testEnvs is used to custom environment variables for deno test

[CLAassistant]

All committers have signed the CLA.

[bartlomieju]

I think it's reasonable solution, @crowlKats thoughts?

[crowlKats]

Yea, think so too. Will test it to see if it works properly

[bartlomieju]

@crowlKats any update?

[bartlomieju]

These docs should be updated to provide more information about its purpose

[ahuigo]

I've provided more information about its purpose.

[bartlomieju]

Suggested change

	## deno.unstable
	## `deno.unstable`

[crowlKats]

@bartlomieju apologies; I tried however no luck getting it to work

[bartlomieju]

@bartlomieju apologies; I tried however no luck getting it to work

Okay, I'll investigate it myself after NYE

[bartlomieju]

I can't get it to work either, putting variables in deno.codeLens.testEnvs has no effect on me. @ahuigo how were you able to make it work?

[ahuigo]

I can't get it to work either, putting variables in deno.codeLens.testEnvs has no effect on me. @ahuigo how were you able to make it work?

@bartlomieju @crowlKats

My test code

import { assertEquals } from "https://deno.land/std@0.164.0/testing/asserts.ts";

Deno.test("test deno testEnvs", async (t) => {
  await t.step("test 1", async () => {
    console.error("env ULTRA_MODE:",Deno.env.get('ULTRA_MODE'))
    assertEquals(Deno.env.get('ULTRA_MODE'), 'debug')
  });
});

Reproduce my test

0. Start this dev Deno plugin.

Press F5 with this PR code.

1. Set testEnvs

In my test, I set ULTRA_MODE to be development123:

2. Then click Debug or Run Test

Though the testEnvs is not visible in the cli line, we can read the correct value development123
in the following figure(See DEBUG CONSOLE and TERMINAL tab)

My device

macOsx: 12.6
cpu: Darwin 21.6.0 arm64 core(10) Apple M1 Pro
vscode: 1.71.2 74b1f979648cc44d385a2286793c226e611f59e7 arm64
deno 1.29.1 (release, aarch64-apple-darwin)
v8 10.9.194.5
typescript 4.9.4
deno extensions: denoland.vscode-deno@3.15.0

[bartlomieju]

@ahuigo when I do the same steps I get following output:

One difference is that I don't see anything in "Debug console" or "Terminal" tabs.

To be honest I'm a bit at loss why that happens. Everything looks correct in the PR.

[ahuigo]

@bartlomieju

1. Have you set testEnvs correctly in workspace .vscode/settings.json?

{
  "deno.codeLens.testEnvs": {
    "ULTRA_MODE": "development123"
  }
}

2. Could you show me your plugin's debug info like this {...config.get("codeLens.testEnvs", {})} ?
   

What's weird to me is that in breakpoint debugging, I can't read the value of env directly, but I can read its value via definition.env.

Perhaps the env is vscode's keyword. https://code.visualstudio.com/docs/editor/variables-reference#_environment-variables

3. What's your version of Vscode?
   I guess it could be a problem with Vscode

[bartlomieju]

I think something is wrong with my setup - I can't hit any debug breakpoints I set in the client code :/ I'm looking into it

[ahuigo]

Try turning off the Deno plugin. @bartlomieju

[bartlomieju]

Try turning off the Deno plugin. @bartlomieju

I tried that, including removing Deno extension completely and it doesn't really help. No breakpoints are ever hit for the "test" command.

[ahuigo]

I don't know if it has anything to do with this problem: #708

[nayeemrmn]

deno.env and deno.envFile should work for this now.