Test: MRU kernel picker

[rebornix]

Refs: microsoft/vscode-jupyter#11904

• Windows @hediet
• macOS @TylerLeonhardt
• anyOS @andreamah

Complexity: 4

Authors: @DonJayamanne , @rebornix

Create Issue

---

We have improved the new MRU kernel picker and enabled that for all Insider users. Please test following scenarios for the platforms you are assigned to.

Initial setup

• Please uninstall both Jupyter and Python extensions and their dependencies
• Reload window and start testing

Test extension recommendation

• Create or open an .ipynb file
  • You might receive extension recommendations but ignore them for now
• Open kernel picker through "Select Kernel" and please test the options (Install Missing Extension) provided to you

Test with extensions installed

Once finished step, you should have both Python and Jupyter prereleases installed. Please test following scenarios

• Verify when you open kernel picker, you have
  • Kernels you used before in the kernel list, and "Select Another Kernel" option at the bottom
• Verify if there is no used kernel before, you see kernel sources directly, including at least "Python Environments..." and "Existing Jupyter Server"
  • Picking kernels from "Python Environments..." will set the environment as the active kernel
  • When running cells, it can prompt you to install ipykernels if it doesn't have it installed already.
  • Note that if you are using default Python environment on Ubuntu, it might not have pip installed, you need to sudo apt install python3-pip. It's currently an known issue Can't create environment in vanilla ubuntu vscode-python#20543

Test new/untitled notebooks

Create a new jupyter notebook and test

• Create a new cell and run cell will prompt the kernel picker
• You can pick kernels from the MRU list and run automatically
• You can run "Select Another Kernel" -> "Python Environments" -> another kernel, and it still runs automatically at the end of the workflow

Reload

After running cells successfully, and then reload the window, please test

• Verify the same kernels (kernel specs and Python environments) are still displayed in the kernel picker