-
Notifications
You must be signed in to change notification settings - Fork 289
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] vscode-jest-tests.v2 Debug Configuration does not replace variables when restarting session #1148
Comments
@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 (microsoft/vscode#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:
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 |
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.
The text was updated successfully, but these errors were encountered: