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
In our extension (vscode-jest), we used the external jest watcher to auto-run tests when the tests or related source files change. In such use case, we used to disable manual test run for the individual test items (TestItem.runnable = false), while still supporting "restarting" the jest watch run for the workspace item. However, after switching to the new RunProfile, we lost the ability to disable the test run on the TestItem level and it would not make sense to fall back to "restart" jest run for the whole workspace...
Similar issue for debugging: we used to only support debugging on the file and individual test level, how to achieve this with the RunProfile?
We end up throwing errors in runTest to prevent the unsupported run/debug, which of course is not ideal. I know this issue has been raised in other discussions, this is now impacting our implementation, hopefully, it will get more urgent priority before release.
VS Code version: Code - Insiders 1.59.0-insider (Universal) (955a1ac, 2021-07-26T05:12:43.446Z)
OS version: Darwin x64 20.6.0
Restricted Mode: No
System Info
Item
Value
CPUs
Intel(R) Core(TM) i7-8700B CPU @ 3.20GHz (12 x 3200)
The text was updated successfully, but these errors were encountered:
connectdotz
changed the title
[Test API] not able to disable individual test run with RunProfile
[Test API] not able to disable individual test run/debug with RunProfile
Jul 26, 2021
thanks, @connor4312 As long as we can enable/disable the runProfiles at the TestItem level and update the UI (run/debug buttons) accordingly, it should work. But maybe we can get away with yet another identifier like tags? Anyway, I left the comment in #129456 for further discussion
Issue Type: Bug
In our extension (vscode-jest), we used the external jest watcher to auto-run tests when the tests or related source files change. In such use case, we used to disable manual test run for the individual test items (
TestItem.runnable = false
), while still supporting "restarting" the jest watch run for the workspace item. However, after switching to the new RunProfile, we lost the ability to disable the test run on the TestItem level and it would not make sense to fall back to "restart" jest run for the whole workspace...Similar issue for debugging: we used to only support debugging on the file and individual test level, how to achieve this with the RunProfile?
We end up throwing errors in
runTest
to prevent the unsupported run/debug, which of course is not ideal. I know this issue has been raised in other discussions, this is now impacting our implementation, hopefully, it will get more urgent priority before release.VS Code version: Code - Insiders 1.59.0-insider (Universal) (955a1ac, 2021-07-26T05:12:43.446Z)
OS version: Darwin x64 20.6.0
Restricted Mode: No
System Info
gpu_compositing: enabled
metal: disabled_off
multiple_raster_threads: enabled_on
oop_rasterization: enabled
opengl: enabled_on
rasterization: enabled
skia_renderer: disabled_off_ok
video_decode: enabled
webgl: enabled
webgl2: enabled
The text was updated successfully, but these errors were encountered: