Add support for refreshing tests in a single project/package/module.

[mrburrito]

Currently, the "Refresh Tests" command and shortcut button in the test view refresh tests across the entire workspace. I have a mono-repo project that I open as a multi-root workspace and I would love to be able to refresh tests from only the specific part of the code I'm currently working as VSCode doesn't always pick up on changes.

The ideal solution would be to add a refresh shortcut next to every expandable test container in the testing view where the Run/Debug/GoTo buttons already pop up on mouseover that would just refresh discovery in that particular module.

[eleanorjboyd]

Hello @mrburrito, thank you for the request. Currently the UI is handled by an API in vscode core, therefore I cannot make any changes to add that button to the test explorer. @connor4312 is this a request you have gotten before or should we create a new feature request for this in core?

In the meantime @mrburrito would it help if when you saved a file it only ran "refresh test" on that specific test file?

Thanks!

[connor4312]

@eleanorjboyd this is actually something you can do by contributing to the testing/item/context menu. Though currently we don't expense the test or controller ID in the when clause, I'll put in a PR for that.

[mrburrito]

The issue is more when VSCode doesn't refresh, which seems to happen more often when there's an error in the file and pytest can't discover tests. That's when I typically find myself wanting to refresh a specific subtree from the test explorer.

[github-actions]

Thanks for the feature request! We are going to give the community 60 days from when this issue was created to provide 7 👍 upvotes on the opening comment to gauge general interest in this idea. If there's enough upvotes then we will consider this feature request in our future planning. If there's unfortunately not enough upvotes then we will close this issue.

[brettcannon]

Thank you to everyone who upvoted this issue! Since the community showed interest in this feature request we will leave this issue open as something to consider implementing at some point in the future.

We do encourage people to continue 👍 the first/opening comment as it helps us prioritize our work based on what the community seems to want the most.