Skip to content

Remote WSL Smoke Test

Martin Aeschlimann edited this page May 11, 2019 · 4 revisions

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

  • close all VS Code WSL windows
  • open a WSL shell and run rm -r ~/.vscode-remote/bin
  • open a new WSL window

Verify that downloading and unpacking the server succeeds and a WSL remote window is opened

  • close all VS Code windows
  • open a WSL shell and run rm -r ~/.vscode-remote/bin
  • in the WSL shell, run code-insiders .

Verify that downloading and unpacking the server succeeds and a WSL remote window is opened

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