Support debugging individual Prism tests in VS Code #311
Conversation
| "preLaunchTask": "Prepare tests debugging", | ||
| "stopOnEntry": false, | ||
| "sourceMap": { | ||
| "${env:BAZEL_EXEC_ROOT}": "${workspaceFolder}", |
| { | ||
| "label": "Prepare tests debugging", | ||
| "type": "shell", | ||
| "command": "export BAZEL_EXEC_ROOT=$(./bazel info execution_root)", |
There was a problem hiding this comment.
IIRC it's beneficial to use the same configuration here, otherwise the Bazel server restarts
| "command": "export BAZEL_EXEC_ROOT=$(./bazel info execution_root)", | |
| "command": "export BAZEL_EXEC_ROOT=$(./bazel info execution_root --config=dbg)", |
There was a problem hiding this comment.
Does bazel info requires starting a server? I tried running it manually with/out the flag and I don't see any difference.
| { | ||
| "id": "test_name", | ||
| "type": "promptString", | ||
| "description": "Enter the test name, e.g. case for running test/prism_regression/case.rb", |
There was a problem hiding this comment.
Should we add a default, to give an example input?
There was a problem hiding this comment.
Also, is there an equivalent to this:
Lines 41 to 45 in bab4eb4
There was a problem hiding this comment.
Personally, I wouldn't use default for example. I think that's what description should do:
Also, is there an equivalent to this:
No it's not available for launch entries. But the input should automatically be filled with the previous value by default. Does that not happen?
Motivation
This is based on @amomchilov's prior work in prism...Shopify:sorbet:Alex/vscode-debugging
Debugging.Sorbet.Prism.tests.in.VS.Code.mp4
I'll also add this to #279 so we remove these stuff before upstreaming.
Test plan
See included automated tests.