Skip to content

Latest commit

 

History

History
133 lines (111 loc) · 5.69 KB

Smoke-Test.md

File metadata and controls

133 lines (111 loc) · 5.69 KB

This page describes the VS Code Smoke test, a manual test case that we execute before we release VS Code to the public on all platforms.

Prereqs

  • For the best debugging experience you'll need node version 0.12.x (or higher)
  • Restore some default settings of VS Code
    • Enable Tabs and the Opened Editors view in the explorer
    • Disable "Auto Save" so that dirty files get some coverage
    • Open the chrome console and watch for exceptions

Setup

Data Loss

  • Verify the following both with dirty files and untitled files
    • Make sure you get asked and can save when closing the editor itself
    • Make sure you get asked and can save when closing from Opened Editors view
    • Make sure you get asked and can save on window close
    • Make sure you get asked and can save on file > quit

Explorer

  • On the desktop create an info.txt file
  • Drag it to the explorer then rename it to README.txt
  • Move README.txt to another folder and then delete it and verify it ends up in the trash
  • Quick open (CTRL+P, ⌘+P) to find the .js files and other files with a similar extension
    • Verify quick open sorting makes sense and it respects fuzzy matching (e.g. 'a.s' should produce 3 results)
  • Verify the Opened Editors view reflects your state of opened editors

Configuration and views

  • Select File > Preferences > User Settings (OS X: Code > Preferences > User Settings)
    • Under editor, change line number to false, save the file, verify that line numbers are turned off without refresh.
  • Select File > Preferences > Keyboard Shortcuts (OS X: Code > Preferences > Keyboard Shortcuts)
    • Change a binding of an action and verify the new binding works. e.g. add: { "key": "ctrl+u", "command": "workbench.action.toggleSidebarPosition" }
  • Verify that all navigation commands from Goto menu work

Search

  • Use Search (CTRL+SHIFT+F, ⌘+SHIFT+F) to find 'body'
    • Verify that 7 results in 4 files show up
    • Verify you can run the search filtering for *.js files
    • Verify you can dismiss files from search results
    • Verify you can replace search results with a replace term

CSS

  • Open file style.css
    • verify quick outline (CTRL-SHIFT-O, ⌘-SHIFT-O)
  • Add an empty rule .foo{}
    • verify you can see a warning in the editor
    • verify you can see a warning from the Problems view
  • Select File > Preferences > User Settings (OS X: Code > Preferences > User Settings)
    • change 'css.lint.emptyRules' from warning to error
    • Go back to style.css, verify that the warning turns into an error.
    • Verify you get css intellisense

Markdown

  • Open readme.md and open the preview side by side
  • Make changes to the readme.md and verify they are reflected live on the preview

JavaScript

  • Open bin/www
    • Show the quick outline (CTRL-SHIFT-O, ⌘-SHIFT-O) verify that entries show up and make sense
    • From the context select Find All References to 'app'
    • From context menu use Rename Symbol to rename a local variable
    • Verify code folding works
  • Open app.js
    • Verify go to definition and peek definition work
    • Format the code

Debugging JavaScript

  • in VSCode switch to debugging viewlet
  • Click on the gear to create a default launch.json file:
    • make sure that VSCode automatically detects ${workspaceRoot}/bin/www as the 'program' attribute
  • set a breakpoint in index.js:6
  • press F5 to start debugging. Verify:
    • workbench transforms into "debug mode" - glyph margin and status bar turns orange
  • open browser at http://localhost:3000/
    • verify the breakpoint in index.js gets hit
  • Verify step over, step in, continue work
  • While stopped, verify:
    • you can hover over values
    • clicking on a stack frame shows variables associated with that stack frame
    • you can add a watch expression
    • you can evaluate a expressions in the debug console
  • Verify you can stop the debug session and that workbench exits "debug mode"

Git

  • Open git viewlet
  • Verify that the changes you made are showing up
    • if not, make some new changes
    • verify the changes in the diff viewer are reflecting the changes you did
    • verify multi select works
  • Commit the changes locally
    • verify that an outgoing change shows up in the status bar of VSCode
  • Clean up: click on the ellipses in the git viewlet and choose 'Undo Last Commit'

Integrated Terminal

  • Open the integrated terminal
  • Run a command and verify the output makes sense (e.g. ls or dir)

Status bar

  • Quickly click on all the actions in the status bar and verify they behave as expected
  • Execute various commands from the status bar (change language mode, indentation…)

Tasks

  • Press (CTRL+SHIFT+B, ⌘-SHIFT-B)
    • Verify the output panel opens and shows errors
    • Verify you can switch output to 'git'
  • Ensure that the executed task detects errors in routes/index.js
    • List all errors with CTRL+SHIFT+M, ⌘-SHIFT-M

Extensions

  • Install an extension that you can easily verify works (e.g. new theme)
    • Verify that the extension gets installed and that on restart of VSCode it works
  • Uninstall the extension and verify it is no longer present after VSCode restarts

Accessibility

  • Turn on
    • OS X: Voice Over
    • Windows: nvda, command palette > 'Toggle use of tab key for setting focus'
  • Tab through the whole workbench and verify what you hear makes sense. Also verify you can tab back into the location from where you started
  • Check high contrast theme

Localization

  • Start code from the command line with --locale=DE
  • Verify all menus and viewlets are in German (or your language of choice)