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

[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.