-
Notifications
You must be signed in to change notification settings - Fork 39k
vscode 1.32.1 jest debug cannot find test files specified if running from current file #70050
Copy link
Copy link
Closed
Labels
*as-designedDescribed behavior is as designedDescribed behavior is as designeddebugDebug viewlet, configurations, breakpoints, adapter issuesDebug viewlet, configurations, breakpoints, adapter issues
Description
- VSCode Version: 1.32.1
- OS Version: Win 7
Steps to Reproduce:
- launch config file:
{
"type": "node",
"request": "launch",
"name": "Jest Current File",
"program": "${workspaceFolder}/node_modules/.bin/jest",
"args": [
"${relativeFile}",
"--config",
"${workspaceFolder}/tests/jest.config.js"
],
"console": "integratedTerminal",
"internalConsoleOptions": "neverOpen",
"disableOptimisticBPs": true,
"windows": {
"program": "${workspaceFolder}/node_modules/jest/bin/jest",
}
}
- Open file that you want to test, e.g. Component.spec.jsx and run the above launch configuration
- Output:
Debugger listening on ws://127.0.0.1:21033/...
For help see https://nodejs.org/en/docs/inspector
Debugger attached.
No tests found, exiting with code 1
Run with `--passWithNoTests` to exit with code 0
In C:\nextgen\ng\ui\common.ui
171 files checked.
testMatch: C:/nextgen/ng/ui/common.ui/utils/**/*.spec.(es6|jsx),C:/nextgen/ng/ui/common.ui/components/**/*.spec.(es6|jsx) - 33 matches
testPathIgnorePatterns: \\node_modules\\ - 171 matches
testRegex: - 171 matches
Pattern: components\form\__tests__\DateTimePicker.spec.jsx - 0 matches
Waiting for the debugger to disconnect...
Does this issue occur when all extensions are disabled?: Yes
It works fine with previous version of VS Code
Reactions are currently unavailable
Metadata
Metadata
Labels
*as-designedDescribed behavior is as designedDescribed behavior is as designeddebugDebug viewlet, configurations, breakpoints, adapter issuesDebug viewlet, configurations, breakpoints, adapter issues