Closed tim-helloquickly closed 5 months ago
@tim-helloquickly, thanks for bringing this to our attention, I can confirm this is a reproducible bug. I am working with the vscode team to see how we can best resolve it (https://github.com/microsoft/vscode/issues/212005).
@tim-helloquickly, I can't seem to be able to reproduce this issue today. Thinking maybe vscode has fixed it already. Can you confirm in your env?
I gave it a shot, I can still reproduce -- here is my configuration:
{
"type": "node",
"name": "vscode-jest-tests.v2",
"request": "launch",
"args": [
"test",
"--watchAll=false",
"--forceExit",
"--testNamePattern",
"${jest.testNamePattern}",
"--testTimeout=100000000",
"--runTestsByPath",
"${jest.testFile}"
],
"cwd": "${workspaceFolder}",
"console": "integratedTerminal",
"internalConsoleOptions": "neverOpen",
"runtimeExecutable": "yarn",
"skipFiles": [
"<node_internals>/**",
"${workspaceFolder}/<node_internals>/**",
"${workspaceFolder}/node_modules/**"
]
},
One thing to note -- if I omit adding a jest configuration to the launch.json and just go with the default, it works properly (so it's specifically the variable substitution
I think maybe I was on an outdated version. It works perfectly now!
Describe the bug A clear and concise description of what the bug is.
To Reproduce Steps to reproduce the behavior:
Expected behavior Expect the same test to run the same way as the first time: jest --runInBand --watchAll=false --testNamePattern 'redacted$' --runTestsByPath /Users/redacted.test.tsx --testTimeout=100000000 --coverage=false
But the second time around,
jest --runInBand --watchAll=false --testNamePattern '${jest.testNamePattern}' --runTestsByPath '${jest.testFile}' --testTimeout=100000000 --coverage=false
Screenshots Here is an output
Environment (please complete the following information):
node -v
: v18.18.0npm -v
oryarn --version
: yarn 1.22.19Prerequisite
Additional context Add any other context about the problem here.