microsoft
/
vscode-remote-release
зеркало из https://github.com/microsoft/vscode-remote-release.git
1
0
Форкнуть 0
Код Задачи Пакеты Проекты Релизы Вики Активность
Страница: Remote WSL Smoke Test
Страницы
Home Profiling Remote Processes Remote Containers Smoke Test Remote Explorer Remote SSH Troubleshooting Remote WSL Smoke Test Roadmap Sanity Check VS Code Servers
4 Remote WSL Smoke Test
Martin Aeschlimann редактировал(а) эту страницу 2020-01-27 15:56:41 +01:00
Содержание

This page describes the Remote WSL Code Smoke test: a manual test suite that we execute before we release a Remote WSL version to the public.

Install

  • Install the latest VS Code stable or insiders in Windows. In the install wizard, allow that VS Code is added to the PATH.
  • Open VS Code and install the Remote - WSL extension

Clean

  • close all VS Code windows, wait a few seconds
  • open a WSL shell
    • ps -ax | grep vscode to check that all VS Code server processes are gone
    • run rm -r ~/.vscode-server/bin (for stable) or rm -r ~/.vscode-server-insiders/bin (for insiders) to delete old VS Code installations.

Opening a Remote- WSL window from the WSL shell

  • clean as described above
  • open a WSL shell
  • run code . (for stable) or code-insiders . (for insiders)
  • Verify that downloading and unpacking the server succeeds and a WSL remote window is opened

Open a Remote- WSL window from VSCode

  • clean as described above
  • open VS Code
  • from the Remote Indicator (on the left if the status bar) invoke Remote-WSL: New Window using Distro.... Pick a distro.
  • Verify that downloading and unpacking the server succeeds and a WSL remote window is opened
  • Use File > Open Folder to open a folder.

Reopen commands

  • In the remote WSL window, open a folder opened, use Remote - WSL: Reopen in Windows : Verify that a Local window on the same folder is opened (using \\wsl$\Ubuntu\ if not in a /mnt/c/ folder)
  • use Remote - WSL: Reopen in WSL to reopen the folder in a distro again

Integrated terminal

  • in the WSL window open a integrated terminal. Verify that the terminal works and shows the WSL file system
  • in the integrated terminal, run mkdir test123, cd test123, and code-insiders .. Verify that a new WSL opens on the folder. Verify that the explorer shows the folder which is empty.
  • in the integrated terminal, run echo "setInterval(() => console.log(i++)" > test.ts. Verify that the explorer is updated and shows the file

Editing

  • open the file. Verify that the typescript extension finds 2 compile errors. Check that the problems view shows the errors and that you can navigate to the error.
  • fix the errors by adding var i = 0; as first line and adding a closing )

Open File and Recent history

  • use Open...'/'Open File... to open a file in WSL. Verify that the custom file picker shows up a and lets you navigate the WSL file system
  • check the Recent history that the opened file appears

Project Management

Help

Smoke Tests