-
Notifications
You must be signed in to change notification settings - Fork 0
NTVS Lightweight Install Manual Test Matrix
Manual testing for lightweight installer
- Start with a machine that does not have visual studio installed.
- Install lightweight VS with Node workload.
- Run through scenarios using this instance.
- Start with a machine has Visual Studio 2015 installed.
- Install lightweight VS with Node workload.
- Run through scenarios on the dev15 install of NTVS.
- Also try the case where NTVS is already installed for Visual Studio 2015.
- Make sure that scenarios still work for both the lightweight instance of NTVS and the vs 2015 instance of NTVS
- Start with a machine has Visual Studio 2015 installed and NTVS installed.
- Install lightweight VS with Node workload.
- Boot the lightweight installer and open a node project.
- Then uninstall the lightweight Node workload.
- Test to make sure the Dev14 NTVS instance has not been broken.
Please run through all scenarios in the NTVS 1.2 Manual Test Matrix.
-
New Project Creation
Duplicate templates listed but otherwise seems fine.
-
Import existing project
-
Editing and IntelliSense
Works fine for basic projects. Note that automatic typings acquisition is intentionally disabled in dev15.
-
Profiling
Currently not accessible easily with our workload. Given the small usage numbers, this seems fine for a preview release. If you do go to the Node.js profiling window manually, things generally don't work great.
-
Deployment
-
Are the titles, descriptions and logos of your workload accurate?
-
Does the workload contain the expected set of required, recommended, and optional components?
-
Does the workload installation UX match your expectations (in terms of required, recommended, and optional components)?
-
With an installation of just the core editor + your workload
- Can you load, build, debug common projects?
- Are there any errors as you navigate around the IDE?
- Are there any components included you’re not expecting (i.e., clutter)?
-
Does the size of the workload match your expectations?
~2GB total. Seems reasonable enough for now give that we depend on webtools .
-
Do we have the right components flagged for supplemental license terms?
This is only relevant for the Node.js component itself it seems. Our Node.js tools component is fine
-
Identify core scenarios and associated telemetry events for P4 dogfooding. See details here: [Core Scenarios & Telemetry info](https://microsoft.sharepoint.com/teams/DD_Willow/_layouts/OneNote.aspx?id=%2Fteams%2FDD_Willow%2FDocuments%2FNotebooks%2FProject%20Willow%20Notes%2FPartner%20Teams&wd=target%28Dogfood%20scenarios.one%7C388404E0-BC21-4E15-9393-246ABF1BDC14%2FNode.js%20development%7C5C766081-8AA9-E94E-9267-4B7474DCB7C0%2F%29 onenote:https://microsoft.sharepoint.com/teams/DD_Willow/Documents/Notebooks/Project%20Willow%20Notes/Partner%20Teams/Dogfood%20scenarios.one#Node.js%20development§ion-id={388404E0-BC21-4E15-9393-246ABF1BDC14}&page-id={5C766081-8AA9-E94E-9267-4B7474DCB7C0}&end)