Skip to content

Manual Test Matrix

Jump to bottom Edit New page
Matt Bierner edited this page Jun 10, 2016 · 13 revisions

Setup

  1. Windows versions:

  2. Windows 7

  3. Windows 8.1

  4. Windows 10

  5. Install Visual Studio, select custom settings, and make sure the Web Tools component is checked during the install.

  6. Visual Studio 2015 + latest updates 1. Community 2. Enterprise (and Pro) 3. Express for Web

  7. Visual Studio 2013 + latest updates 1. Community 2. Express for Web 3. Ultimate (and Pro, Premium)

  8. Visual Studio 2012 + latest updates 1. Ultimate (and Pro, Premium)

  9. Language settings

  10. English VS on English Windows

  11. Chinese VS on English Windows

  12. German VS on English Windows

  13. English VS on Chinese Windows

  14. Chinese VS on Chinese Windows

  15. English VS on German Windows

  16. German VS on English Windows

  17. TypeScript extension [optional, but required for TypeScript-based projects]:

  18. Visual Studio 2015: http://download.microsoft.com/download/6/D/8/6D8381B0-03C1-4BD2-AE65-30FF0A4C62DA/TS1.6.2-D14OOB.23313.00/TypeScript_Full.exe

  19. Visual Studio 2013: http://download.microsoft.com/download/4/4/3/443F86B7-A89F-48E6-AC96-0AAC2A910A29/TS1.6.2-VUOOB.40914.00/TypeScript_Dev12.exe

  20. Visual Studio 2012: https://visualstudiogallery.msdn.microsoft.com/ac357f1e-9847-46ac-a4cf-520325beaec1

  21. Node.js Tools for Visual Studio (NTVS)

  22. Visual Studio 2015: https://github.com/Microsoft/nodejstools/releases/download/v1.1.Dev-9.17.2015/NTVS.Dev.2015-09-17.VS.2015.msi

  23. Visual Studio 2013: https://github.com/Microsoft/nodejstools/releases/download/v1.1.Dev-9.17.2015/NTVS.Dev.2015-09-17.VS.2013.msi

  24. Visual Studio 2012: https://github.com/Microsoft/nodejstools/releases/download/v1.1.Dev-9.17.2015/NTVS.Dev.2015-09-17.VS.2012.msi

  25. Install Node.js (test all versions)

  1. Install Azure Tools [optional, but required for web publishing support]
  2. Azure Tools for VS 2015: http://go.microsoft.com/fwlink/?LinkId=534216
  3. Azure Tools for VS 2013: http://go.microsoft.com/fwlink/p/?linkid=323510
  4. Azure Tools for VS 2012: http://go.microsoft.com/fwlink/p/?linkid=323511
  5. [OPTIONAL] Other extensions
  6. Web Essentials 1. VS 2015: https://visualstudiogallery.msdn.microsoft.com/ee6e6d8c-c837-41fb-886a-6b50ae2d06a2 2. VS 2013: http://visualstudiogallery.msdn.microsoft.com/56633663-6799-41d7-9df7-0f2a504ca361 3. VS 2012: http://visualstudiogallery.msdn.microsoft.com/07d54d12-7133-4e15-becb-6f451ea3bea6
  7. ReSharper: https://www.jetbrains.com/resharper/

Make sure everything installed OK**

Test basic scenarios

Use the following Templates:

  • Create a new Starter Azure Node.js Express 3 Starter Project (JavaScript) in c:\src using the project template in Node.js -> JavaScript
  • Create a new Starter Azure Node.js Express 3 Starter Project (TypeScript) in c:\src using the project template in Node.js -> TypeScript

If you are testing io.js follow the "Configuring your project to use io.js" steps to configure your project:

Walk through these steps with both templates

  • Wait for npm install to finish executing in the background (see details in the Output npm pane)
  • Set a breakpoint in app.js at the line (or app.ts):
var app = express()
  • Set a breakpoint in routes\index.js (or routes\index.ts) at the line that begins with
res.render('index'
  • F5 to start debugging
    • Ensure the browser launches (http://localhost:1337)
    • Ensure both breakpoints are hit
    • Ensure the url loads successfully
  • Walk through the “Profiling” and “Start your profiling session” sections in the Profiling docs, and verify things look as they do in the screenshots
  • Walk through the “Browsing/Installing new npm packages in the GUI” section
  • Walk through the Test Explorer documentation:
  • Browser/Node.js-side editing
    • Switch to Full Intellisense for Node.
    • Create a new directory named “hello”, and right click to add a new javascript item “item1.js” to the directory
      • Verify that the directory display name changes to “hello (node)”
      • Verify that Ctrl + Space in item.js produces a completions list with “process” in it.
      • Right click the directory, and select “Set as Content (Browser code)”
      • Verify that the directory display name changes to “hello (browser)”
      • Verify that the build action of the item.js file is now set to “Content”
      • Add a new javascript file, “item2.js” to the directory, by right clicking the directory and using “Add New Item”
      • Verify that the directory name is still set to “hello (browser”)
      • Ctrl + space in the “item2.js” file that has opened, and verify that “document” appears in the completions list
      • F2 to change the name of the directory, and verify that the edit label is “hello”
      • Type a new directory name - “goodbye”
      • Verify that the name of the directory is “goodbye (browser)”
  • Right click the project, Add new item, select the “Dockerfile” item template, and verify that the file is generated successfully.
  • Interactive window
    • Open the Node.js Interactive Window using Ctrl+K, N
    • Run .npm install azure --save-dev
    • Verify that the output is readable and doesn’t include any odd characters once the command finishes executing
    • Verify that a new entry has appeared in the npm > dev node in Solution Explorer and there are no errors/warnings
Add a custom footer
Add a custom sidebar
Clone this wiki locally