"test" is not an allowed value for the "request" property of launch configs configurations

[weinand]

The documentation at https://code.visualstudio.com/docs/python/testing#_debug-tests says that a value "test" can be used for the "request" property of launch configs configurations.

Please note, that this is neither supported by VS Code nor by DAP and it will break an unknown number of assumptions and result in a bad user experience (e.g. microsoft/vscode#119903). The only supported values are "launch" and "attach".

[brettcannon]

What would the preferred way be for us to be able to denote which launch configuration is meant to be used when debugging a test when launched from our test explorer?

[weinand]

@brettcannon you can either:

• add a new property to the schema of your "python" launch config (this property is only allowed on "python" launch configs and will result in an error in launch configs of different types).
• or you could add a new independent (orthogonal) property that is allowed in all launch configs. VS Code's "serverReady" feature is a good example for how to add a property to all launch configs. See https://github.com/microsoft/vscode/blob/7208128b8187d942419237855c324877d096cf43/extensions/debug-server-ready/package.json#L22-L138.

[kimadeline]

Verification steps:

1. Make sure you have "python.experiments.optInto": ["All"], in your user settings. If not, add it and reload.
2. Open a workspace with some python files in it
3. Add the following configuration to your launch.json file (create it first if necessary):

        {
            "name": "Some configuration",
            "type": "python",
            "request": "test",
            "console": "integratedTerminal"
        },

4. Make sure that there's a squiggle under "test", and that the only accepted values are launch or attach

[rzhao271]

I'm not seeing any squiggles on VS Code Insiders.

In my settings.json: "python.experiments.optInto": ["All"]
Python extension version: v2021.9.1160333636-dev

[karthiknadig]

@rzhao271 can you try with this vsix: https://pvsc.blob.core.windows.net/extension-builds/ms-python-insiders.vsix

[rzhao271]

I got it to work.
My launch config was invalid because it was just that block of JSON. When I created a new launch config, things got put into the proper format.