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
{{ message }}
Repository navigation
Add action buttons for Run/Debug per item in the Test View #4277
Hook up hover buttons in the tree view to handle 'Run, Debug'.
This functionality would be the same as that for the prior task enabling these items, but would act on only the item selected and its children.
Send in the runId of the Tests structure to the 'Run Test' API that exists today. And if there are multiple then we run them one by one.
Add a context-menu to each test explorer test item, and add the 'Run Failed' option to the menu.
This will run only the failed subordinate items that failed. That is, if a suite is selected, only the functions with a failed status will be re-run. Same for file. Same for function (what happens if the user selects a successful test and says 'run failed') is this context-menu-item only valid for suites/files/folders?
If the VS Code API does not provide live updates to the icons shown, then just show them all, all the time, and have them work when they make sense.
Test for completion:
Clicking the 'Run' or 'Debug' button next to an item will run that entire item (with debugger on Debug):
For a function, just that function
For a Suite, all functions in that suite.
For a File, all functions in that folder
Select a suite that contains 1 or more failed tests and choose 'Run Failed' from the context menu in the test explorer.
Only the test that had failed status should be run, if their status changed the status should be reflected in the explorer.
Activity
Add commands to run, debug and open tests (#4332)