[Feature request] Multi-root: Allow disabling tests (discovery/prompts/...) for a root

(Re-filing https://github.com/microsoft/vscode/issues/97842)

Multi-root workspaces are motivated like this:

For example, you might have a repository with a product’s documentation which you like to keep current when you update the product source code.

Exactly my use case. However, in such a multi-root workspace, I am now often confronted with the choice of one of the two folders for various operations. This is mostly fine, but really useless when it comes to testing: my documentation repo does not offer any testing whatsoever. So it’s unnecessary work for me to select the product repo each time I discover tests, or run all tests, etc.

Maybe I have missed it, but a setting to disable all test functionality would be highly appreciated. I would then put this setting into the .vscode/settings.json in the documentation repo and be very happy. (If this already exists, I’d be even happier, but I haven’t found it yet.)

[bersbersbers]

@bersbersbers this prompt you showed should only be displayed if you trigger test discovery (i.e. if you click on the “discover tests” button in the test explorer view or run the Python: Discover Tests command).

I am not sure. I’d say “no”, I get this prompt the first time I open the “Test” panel in each session.

I cannot say if automatic test discovery is on or not, but I have set this in my user settings:

"python.testing.autoTestDiscoverOnSaveEnabled": false,

You can also disable all test frameworks by adding the following to the .vscode/settings.json file in your docs repo:

 "python.testing.unittestEnabled": false,
 "python.testing.pytestEnabled": false, 

Seems plausible, but does not work. This is my docs repo .vscode/settings.json:

{
    "python.testing.promptToConfigure": false,
    "python.testing.unittestEnabled": false,
    "python.testing.pytestEnabled": false,
    "python.testing.nosetestsEnabled": false,
}

Still,

1. I get the “No test framework configured (unittest, pytest or nosetest)” prompt
2. When clicking “Discover Tests”, I still get a prompt to select the workspace (code or doc - where doc makes no sense, so the whole prompt makes no sense as only a single option remains).

[karrtikr]

I see, I’m closing this issue for now, feel free to leave a comment if anyone sees this and we’ll be happy to have a look again.