command 'python.configureTests' not found

[starmandeluxe]

Environment data

• VS Code version: 1.33.1
• Extension version (available under the Extensions sidebar): 2019.4.12954
• OS and version: MacOS Mojave 10.14.4
• Python version (& distribution if applicable, e.g. Anaconda): 3.7.3
• Type of virtual environment used (N/A | venv | virtualenv | conda | ...): N/A
• Relevant/affected Python packages and their versions: XXX

Expected behaviour

Should get an additional menu to select and then install the test framework.

Actual behaviour

Error pops up in VS Code at the bottom saying: "command 'python.configureTests' not found"

Steps to reproduce:

1. Ctrl+Shift+P
2. Type "Python: Configure Tests"
3. Click the first option

Logs

Output for Python in the Output panel (View→Output, change the drop-down the upper-right of the Output panel to Python)

N/A

Output from Console under the Developer Tools panel (toggle Developer Tools on under Help; turn on source maps to make any tracebacks be useful by running Enable source map support for extension debugging)

Error: command 'python.configureTests' not found
    at Proxy._tryExecuteCommand (workbench.main.js:sourcemap:3027)
    at r.then.i (workbench.main.js:sourcemap:3027)
    at process._tickCallback (internal/process/next_tick.js:68)

[karrtikr]

Unfortunately, I am not able to reproduce this error.

Please ensure the extension has activated by opening a python file. Also please try removing .vscode, restart VSCODE, re-installing extension to see if that works.

[starmandeluxe]

@karrtikr I performed the actions you recommended and there was no difference in behavior:

The error still shows, but if I click on the top notification I am able to choose a test framework, however it still does not find my test even though I have a valid unit test file in my directory.

[DonJayamanne]

Please could you provide:

• The contents of your .vscode/settings.json file
• Sample repo so we can repro this issue at our end
• Open Python Test Log output panel and let us know what you see there

[Cetlan]

I have a similar problem. I don't know if it's exactly the same thing, but this might help. In my development environment (due to an unfortunate dependency on buildout), the python script I have to specify is actually a wrapper, not "real" python. If that script is set as pythonPath in the settings when vscode loads, all the discover/run/configure test commands are not found when trying to run them (I've checked the command registry in the debugger, they're really missing, even though they're in the menu). If I select a "real" python, those commands reappear and I can then set the python wrapper again and things will seem to work fine.

[DonJayamanne]

the python script I have to specify is actually a wrapper, not "real" python.

The python executable specified in pythonPath needs to be something that can be launched in code as a procecss (using spawn).

[Cetlan]

The python executable specified in pythonPath needs to be something that can be launched in code as a process (using spawn).

Using the wrapper works for everything else so far aside from that command initialization. It's just python script that starts with
#!/bin/python (or whatever interpreter was used to run buildout), and loads in the paths the buildout used before basically running whatever was specified. So I don't know if thats something vscode can spawn.

And this might not be the case at all for the OP, but it is the one place where I've reproduced these missing commands anyway.

[DonJayamanne]

Unfortunately the extension doesn't parse the contents of the file to respect the bang (!). Hence that will not work without changes to the extension to support this specific scenario.

[DonJayamanne]

Closing this issue as its been over 4 weeks, since the information was requested.
We'll be happy to reopen the issue when the requested information has been provided.