Support Testing of VS Client Outline

What?

This hands-on exercise allows VersionOne's Support Team to verify that the Visual Studio Client is supportable.

When and Where?

When: Wed, December 4th 2013, 3 - 4 PM

Office: Alpharetta

GoToMeeting: https://www1.gotomeeting.com/join/809334697

Why?

For VersionOne to feel confident that a product is supportable, each product should meet the Support Team's criteria for the installation process, configuration, and usage characteristics.

Who?

• Testers: Mark Irvin, Victor Hernandez, Sophia Garcia
• Observers: The Product Owner and the Development Team

How?

Dev Team Setup Steps

• In the morning (before 12), run the first two steps from Mark's steps below to get a "preloaded" environment ready for Mark.
• Replace the TODO placeholders below for Mark once the VMs load.

Mission 1: Tester Team Visual Studio Client Testing Plan

Amazon instances

• Mark: visualstudio2013ult_Mark.compute-1.amazonaws.com (54.224.143.49)
• Victor: visualstudio2013ult_Victor.compute-1.amazonaws.com (50.16.67.241)
• Sophia: visualstudio2013ult_Sophia.compute-1.amazonaws.com (54.227.191.220)

Steps

• Using Remote Desktop Connection (mstsc.exe), log On to the VM for Visual Studio at the IP address for your machine above
  • Username is v1deploy
  • Get the password over HipChat, or
  • Find credentials in the v1chef\boot_ec2.sh file if you have access to the v1chef repository (private to VersionOne for now)
• Open a web browser and navigate to the Visual Studio Client's staging App Catalog entry at http://appcatalogstage.azurewebsites.net/app/index.html#/Details/VersionOne.Client.VisualStudio.
• Download the vsix file and install it.
• Open the Documentation link from the App Catalog entry
• In Windows Server 2012 you can use the Windows key to bring up the programs list
• Open Visual Studio and configure the client-- see the Documenation link from the App Catalog entry) to connect to:
  • Application URL: https://www14.v1host.com/v1sdktesting
  • UID / PWD: admin / admin
• Tester testing mission:
  1. Test against the list of updates found in the app catalog.
  2. Test against the happy path for the IDE clients.
  3. Test against your own acceptance criteria.
• Observers goals:
  • Take notes on what testers test
  • Don't guide unless asked
• Post Testers' testing:
  • Dev testing mission: demo key improvements and fixes to team to ensure no 'blow ups' :-D
  • Questions / Discussion

Mission Output

• Is the build Supportable? Does the current build meet Mark and team's Supportable criteria?
  • And, document these criteria
• New Bugs / Issues added into GitHub Issues
• Suggestions discussed and added into GitHub Issues for categorization and prioritization
• Findings from Support Testing on 2013-11-06

Mission 2: Mark Test Environment Automation Testing Steps

Mark's Machine's Required Software

• Install Git with Git Bash.
  • Can be installed via [Chocolatey]((http://chocolatey.org/) with the command cinst git, or manually from the Git site.
• Install Ruby 1.9.3
• Once installed open a command prompt and type gem install bundler to install Bundler.

Pending completion of the first mission, we can procede to the next mission:

• Open Git Bash
• Clone the v1chef repo git clone https://github.com/versionone/v1chef -- gets the scripts needed to automate creating the VMs in Amazon
• Follow the first few steps in the QUICKSTART of the v1chef README.md. Doing so will accomplish the following and report all address details to you:
  • Create a VM with VersionOne
  • Create a separate VM with Visual Studio

Mission Output

• How was the automated deployment experience? What would make the EC2 instance more amenable to Mark's needs?
• New Bugs / Issues added into GitHub Issues
• Suggestions discussed and added into GitHub Issues for categorization and prioritization