You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Unfortunately, these settings don't seem to affect the "Debug Tests" feature, including UI buttons in the Testing tab and the "Debug Test at Cursor" / "Debug Tests in Current File" menu options.
When using the standard "Start Debugging" option, both the default and the custom configuration (if specified directly) work. Additionally, "logToFile": true also doesn't apply to tests, but works for normal run, suggesting that the configuration might be completely ignored for tests.
Moving these settings to a .code-workspace file doesn't help.
Steps to reproduce:
The sample project consists of a single file and configured to use pytest, python 3.12.1:
The debugger doesn't step into any of these logging.getLogger() when run as test, and successfully does it if run directly.
When the debugger skips a step-in, the notification appears:
Frame skipped from debugging during step-in.
Note: may have been skipped because of "justMyCode" option (default == true). Try setting "justMyCode": false in the debug configuration (e.g., launch.json).
Diagnostic data
Python version (& distribution if applicable, e.g. Anaconda): 3.12.1
Type of virtual environment used (e.g. conda, venv, virtualenv, etc.): Venv
Value of the python.languageServer setting: Default
Output for Python in the Output panel (View→Output, change the drop-down the upper-right of the Output panel to Python)
Type: Bug
Behaviour
Expected vs. Actual
I tried several ways to disable justMyCode, but unfortunately none of them worked for tests.
"debugpy.debugJustMyCode": false
to my settings.vscode/launch.json
as follows:Unfortunately, these settings don't seem to affect the "Debug Tests" feature, including UI buttons in the Testing tab and the "Debug Test at Cursor" / "Debug Tests in Current File" menu options.
When using the standard "Start Debugging" option, both the default and the custom configuration (if specified directly) work. Additionally,
"logToFile": true
also doesn't apply to tests, but works for normal run, suggesting that the configuration might be completely ignored for tests.Moving these settings to a
.code-workspace
file doesn't help.Steps to reproduce:
The sample project consists of a single file and configured to use pytest, python 3.12.1:
The debugger doesn't step into any of these
logging.getLogger()
when run as test, and successfully does it if run directly.When the debugger skips a step-in, the notification appears:
Diagnostic data
python.languageServer
setting: DefaultOutput for
Python
in theOutput
panel (View
→Output
, change the drop-down the upper-right of theOutput
panel toPython
)User Settings
Extension version: 2024.1.10391007
VS Code version: Code 1.86.1 (Universal) (31c37ee8f63491495ac49e43b8544550fbae4533, 2024-02-07T09:09:01.236Z)
OS version: Darwin arm64 23.3.0
Modes:
System Info
canvas_oop_rasterization: enabled_on
direct_rendering_display_compositor: disabled_off_ok
gpu_compositing: enabled
multiple_raster_threads: enabled_on
opengl: enabled_on
rasterization: enabled
raw_draw: disabled_off_ok
skia_graphite: disabled_off
video_decode: enabled
video_encode: enabled
webgl: enabled
webgl2: enabled
webgpu: enabled
A/B Experiments
The text was updated successfully, but these errors were encountered: