-
Notifications
You must be signed in to change notification settings - Fork 309
Closed
Labels
Description
Environment
vscode-jest version
: v6.1.1node -v
: v20.10.0npm -v
oryarn --version
: 10.2.3npm ls jest
ornpm ls react-scripts
(if you haven’t ejected):
...@3.7.0
├─┬ ..../eslint-config-ts@1.6.6
│ └─┬ eslint-plugin-jest@27.6.0
│ └── jest@29.7.0 deduped
├─┬ ...@3.7.0 -> ./
│ └── jest@29.7.0 deduped
├── jest@29.7.0
└─┬ ts-jest@29.1.1
└── jest@29.7.0 deduped
- your vscode-jest settings if customized:
- Operating system: ubuntu (WSL2)
Prerequisite
- are you able to run jest test from the command line? yes
- how do you run your tests from the command line? (for example:
npm run test
ornode_modules/.bin/jest
) npx jest
Steps to Reproduce
- set the setting
"jest.nodeEnv": {
"MYENV": "TRUE"
}
- use that property in a test
When running the test without debugging, it works and the env variable is set in the process.
But when using the debugging, the env variable is empty.
bonqus and jjliggett