Test UI changes for the Python interpreter selection quickpick

[kimadeline]

Refs: #16971

• macOS @bpasero
• linux @karthiknadig
• windows @eamodio

Complexity: 4

Create Issue

---

Requirements:

1. Make sure you have "python.experiments.optInto": ["All"], in your user settings. If not, add it and reload.
2. Create 2 workspaces with Python files in it, and create a virtual environment in one of them (python -m venv .venv). Let's name them with and without
3. Python 3 available on your machine
4. Use the following build of the Python extension: https://github.com/microsoft/vscode-python/suites/3575138020/artifacts/85925936

🔍 Please report anything you find unintuitive, redundant, or missing.

Scenario 1: python .defaultInterpreterPath not set, no virtual environment

1. Make sure that the python.defaultIntepreterPath entries in your user and workspace settings are at their default value python
2. Open the without workspace, wait for the extension to load, and click on the interpreter in the status bar on the bottom left:
   
3. Make sure that the interpreter that is currently highlighted in the quickpick is the same as the one that is currently selected (same path being shown in Current: ....), that the entry label starts with star ⭐️ , and that its description says "Recommended"
4. Make sure that there is no "Use Python from python.defaultInterpreterPath setting" entry

Scenario 2: python.defaultInterpreterPath set, no virtual environment

1. Set one of the python.defaultIntepreterPath entries in your user and workspace settings to a valid Python interpreter path that is not python (for example /usr/local/bin/python3)
2. Open the without workspace, wait for the extension to load, and click on the interpreter in the status bar on the bottom left
3. Make sure that the interpreter currently selected has the same path as what's in python.defaultInterpreterPath
4. Make sure there is a "Use Python from python.defaultInterpreterPath setting" entry with the same path, that this entry is highlighted, and that it's the second on the list starting from the top (right below "Enter interpreter path...")

Scenario 3: python.defaultInterpreterPath not set, with virtual environment

1. Make sure the python.defaultIntepreterPath entry in your user and workspace settings are at their default value python
2. Open the with workspace, wait for the extension to load
3. Make sure that the interpreter in the status bar on the bottom left is the .venv virtual environment you created above, and then click it
4. Make sure that the interpreter that is currently highlighted in the quickpick is the .venv one, that the entry should be the second one from the top, that its label starts with a star ⭐️, and that its description says "Recommended"
5. Make sure that there are no duplicate entries with the same interpreter path
6. Make sure that there is no "Use Python from python.defaultInterpreterPath setting" entry

Scenario 4: python.defaultInterpreterPath set, with virtual environment

1. Set one of the python.defaultIntepreterPath entries in your user and workspace settings to a valid Python interpreter path that is not python (for example /usr/local/bin/python3)
2. Open the with workspace, wait for the extension to load, and click on the interpreter in the status bar on the bottom left
3. Make sure that the interpreter currently selected has the same path as what's in python.defaultInterpreterPath
4. Make sure there is a "Use Python from python.defaultInterpreterPath setting" entry with the same path, that this entry is highlighted, and that it's the second on the list starting from the top (right below "Enter interpreter path...")
5. Make sure that the third entry is the .venv environment, that its label starts with a star ⭐️, and that its description says "Recommended"

[bpasero]

I am not feeling very comfortable changing my main dev machine to Python 3, given I have only 2 installed and I don't want to mess with it (as it is needed to yarn VSCode for dev purposes).

What is the recommendation to get an isolated environment on macOS in this case? I found pyenv but wonder if that could mess with my main Python too.

[bpasero]

Nevermind, I got help on that.

I found a few issues that make me wonder whether I tested the right version, I installed [email protected] and set to use insiders "Daily".

[kimadeline]

Hi @bpasero, would you mind testing again with a release build? This one: https://github.com/microsoft/vscode-python/suites/3575212483/artifacts/85927474

Let me update the test plan with the build, sorry about that.

After double-checking it it might be outdated, will investigate our builds first.

Double-checked, this build should work: https://github.com/microsoft/vscode-python/suites/3575138020/artifacts/85925936
Updating the test plan.

[sandy081]

@bpasero Not sure if your un-assignment is intended as the checkbox is not checked in the description. Hence assigning you again. Please unassign and check if you are done with testing here.

[eamodio]

@kimadeline For me all scenarios failed except for #1. FYI, I'm in Windows 11 on ARM64 if that matters.

[kimadeline]

@eamodio which version of the extension were you using? Could you set the python.logging.level user setting to "Debug" and copy the content of the "Python" output channel for each failing scenario?

I'm in Windows 11 on ARM64 if that matters

Hmmm it shouldn't, but you never know 🤔

[eamodio]

@kimadeline I updated the issues I filed with screenshots and logs. Although Scenario 3 started working and can no longer reproduce.

[bpasero]

It turns out none of my testing was for the right latest version. For the future it would be helpful to indicate exactly which build to use.