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
Test Explorer context menus should re-use same launch configuration #1951
In hindsight, this sort-of makes sense. While we can't add custom context menu items here, it isn't clear that the Run/Debug options on there should use the custom templates.
There isn't really a clean way to do this - as we can't just keep track of the last config per-test, as you can run a while file/group at a time (eg. run a group with a config, then want to re-run an individual test). Since we can't alter the text on the context menu dynamically this was already going to be a less-than-ideal user experience, we should wait until there's a better way to handle this (like dynamic context menus).
I don't think it makes sense to do this - we should use profiles for different kinds of launches and not have the tree behave differently depending on how you last run the test.
There's an open issue about using profiles for the CodeLens configs at #3607
Activity
DanTup commentedon Sep 17, 2019
In hindsight, this sort-of makes sense. While we can't add custom context menu items here, it isn't clear that the Run/Debug options on there should use the custom templates.
DanTup commentedon Jun 1, 2020
We could perhaps have a ("re-run with last config") option, toggled only if it's available for the node and put it at the top?
DanTup commentedon Jul 28, 2020
There isn't really a clean way to do this - as we can't just keep track of the last config per-test, as you can run a while file/group at a time (eg. run a group with a config, then want to re-run an individual test). Since we can't alter the text on the context menu dynamically this was already going to be a less-than-ideal user experience, we should wait until there's a better way to handle this (like dynamic context menus).
DanTup commentedon Jul 31, 2025
I don't think it makes sense to do this - we should use profiles for different kinds of launches and not have the tree behave differently depending on how you last run the test.
There's an open issue about using profiles for the CodeLens configs at #3607