In 2010, Microsoft released a bold new featureset to support management of virtual test environments. "Lab Management" provided the ability to easily spin up test environments, perform automated build and deployments, run automated tests, and collect diagnostic data. Unfortunately, many teams were discouraged by the infrastructure requirements. Now, with Visual Studio 2012 and standard environments, even small teams or groups that can't use Microsoft's Hyper-V can still benefit from lab management. This session will demonstrate how to configure your existing environments for many of the same compelling features formally available only with Hyper-V.
1. Managing Test Labs Without the Headaches
Visual Studio 2012
Imaginet and ALM…
Efficiently Build Better Software
2. Agenda
• Lab Management Overview
– Demo: Creating a Standard Environment
• Version Comparison
– Agents
– Standard Environments
• Workflow Impact
– Demo: Implementing a BDT workflow in a
Standard Environment
3. Test Environments
• Group of machines configured to support testing of a
system
Web
• Generally… Server App
Server
– Shared resources
– IT and/or Dev Controlled
• Configuration
• Reconfiguration
• Backup/Restore
• Deployment
Database
Server
4. Lab Management
• Create and manage virtual or standard test
environments
• Take snapshots or revert to existing snapshots for
virtual environments
• Interact with test environment through the
Environment Viewer
• Support for shared or isolated virtual environments
• Define and use test settings for environments
• Facilitate automated build/deploy/test
5. Virtual and Standard Test Environments
Environment #1 Environment #2a Environment #2b
Virtual Machine Server(s)
Environment Environment
#2a #2b
VM1 VM4
VM2 VM5
VM3 VM6
6. Logical Lab Architecture
Microsoft Test Manager (Lab Center and Environment Viewer)
Team Foundation Server Standard
Environment(s)
Lab Management
System Center Virtual
Test Management Machine Manager
(SCVMM)
Build Management
Library Server(s)
Hyper-V Host(s)
Environment(s)
Test
Work Item Tracking Controller(s)
Virtual
Version Control Build
Controller(s)
Reporting
8. Agenda
• Lab Management Overview
– Demo: Creating a Standard Environment
• Version Comparison
– Agents
– Standard Environments
• Workflow Impact
– Demo: Implementing a BDT workflow in a
Standard Environment
9. Lab Management 2010
• First Generation product
• Core Functionality
– Physical & Virtual Test Environments
– Build-Deploy-Test (BDT) Workflow*
– Test Environment Snapshots*
– Environment Viewer
– Identical network-isolated environments*
* Out-of-the-box for Hyper-V only
10. Changes in Lab Management 2012
• Simplified Agent Configuration
• SCVMM 2012 and Clustered Host Support
• Standard Environments
11. Simplified Agent Configuration
• Visual Studio 2010
– Three agent types installed on client machine:
• Test
• Build
• Lab Agent
• Visual Studio 2012
– Single agent (Test) automatically installed during
environment creation
12. Agents
• Installed on “client” machines
• Three agent types:
– Test Agent – Enables automated
testing on the client machine
– Build Agent – Enables
automated deployment to the
client machine
– Lab Agent – Enables Network
Isolation (2010 Only)
• Available on the Lab
Management media (Test and
Lab) or the TFS media (Build)
• Can be installed/maintained
using the VMPrepTool
14. Build Controllers and Agents
Team
Automated build and deployment is
Foundation
through Build Controllers and Agents.
Server
Build Standard Virtual
(Deploy) Environment (2012) Environment with
Build
Controller(s) with Build Agents Build Agents
Build
(Compile)
System #1 VM #1
Build
System #2 VM #2
Server(s)
(with Build
Agents) Etc. Etc.
15. Lab Agents (2010 Only)
Virtual Machine Server(s)
Environment A Environment B Environment C
VM1+Agent VM1+Agent VM1+Agent
VM2+Agent VM2+Agent VM2+Agent
VM3+Agent VM3+Agent VM3+Agent
16. Standard Environments
• Environments composed of non-Hyper-V machines:
– Physical machines
– VMWare
– Other non-Microsoft virtualization technologies
• Lab management features available without SCVMM
and Hyper-V:
– Automated Deploy
– Automated Testing
• Easy to get started testing using Lab Management
17. Environment Comparison
Virtual Standard
Capability
Environments Environments
Testing
Run manual tests Supported Supported
Run coded UI and other automated tests Supported Supported
File rich bugs using diagnostic adapters Supported Supported
Build deployment
Automatic build-deploy-test workflow Supported Supported
Environments creation and management
Automatically install test agent into machines
Supported Supported
of the environment
Create environment from VM template Supported Not supported
Start/stop/snapshot environment Supported Not supported
Connect using Environment Viewer Supported Supported
Run multiple copies of an environment at the
Supported Not supported
same time using network isolation
18. Comparison of Installation Process
Virtual Environments Standard Environments
• Prerequisites: • Prerequisites:
– TFS 2010 or TFS 2012 – TFS 2010 or TFS 2012
• SCVMM Admin Console on the TFS
– Virtual machine host server(s):
• Windows Server 2008 or later (R2
or 2012 recommended)
• Hyper-V
• SCVMM Server
• Library server
• Process:
• Process: – Install agents on existing physical
– Configure Lab Management using (or non-Hyper-V virtual) machines
the TFS Admin Console • „Automatic‟ with TFS 2012
– Import virtual machines – Create environments based those
machines
– Install agents as needed
– Create environments, templates,
etc. in library
19. Agenda
• Lab Management Overview
– Demo: Creating a Standard Environment
• Version Comparison
– Agents
– Standard Environments
• Workflow Impact
– Demo: Implementing a BDT workflow in a
Standard Environment
20. Build Workflow
DEV
DEV
DEV
C#
EXE
TFS Version
Control
TFS Build Process
23. Implementing a BDT Workflow
• Configure Team Foundation Build Service for your
team project collection
• Set up a test controller and register it with your team
project collection
• Set up a lab environment
– SCVMM, or
– Standard (physical, VMWare, other virtualization platform)
• To run automated tests after deployment
– Create a test plan with test case(s)
– Create automated test(s) and link to test case(s)
– Create test settings for the automated test(s)
• Create deployment scripts for your application(s)
• Configure BDT workflow
26. Imaginet‟s New Visual Studio 2012 Website!
Visit Imaginet‟s new Visual Studio 2012 website, your one-stop
hub for all your Visual Studio 2012 needs!
http://visualstudio.imaginet.com
27. For attendees of today‟s session that fill out the survey
FREE Imaginet On Demand
Web Training Subscription Offer
Complete our Post-Webcast survey, and receive 1
free Imaginet On Demand web training
subscription, good for 1 person for 1 month!! The
survey will be emailed to you immediately after this
webcast is over.
What is Imaginet On Demand? Imaginet is proud to announce our newest
web-based training program called Imaginet On Demand, your source for the
best Application Lifecycle Management (ALM) training on the internet.
Imaginet On Demand is a subscription-based training program centric to the
Visual Studio ALM tools, including Visual Studio, Team Foundation Server
(TFS), Microsoft Test Manager, and Microsoft Visual Studio Lab Management.
Learn the new tools of Visual Studio at your pace, from wherever you want.
It's that simple!
28. Need Help with YOUR Lab Management Setup?
Imaginet’s Visual Studio 2012
Lab Management 10-day Quickstart
• Includes designing, installing, and configuring Microsoft‟s
virtual test lab management software.
• Learn best practices for using with Lab Management
• Support and training for your team
• Includes a high-level ALM assessment
Interested? Just email us at info@imaginet.com.
29. Top Gun Academy Training Classes
• Other Imaginet Training Classes
– ALM
• Microsoft Visual Studio & TFS 2012 – Skills Upgrade (2 days)
• Overview Training with Microsoft Visual Studio 2012 ALM Tools (4 days)
• Overview Training with Microsoft Visual Studio 2010 ALM Tools (4 days)
• Testers Training with Microsoft Visual Studio 2012 ALM Tools (4 days)
• Testers Training with Microsoft Visual Studio 2010 ALM Tools (4 days)
• Developers Training with Microsoft Visual Studio 2012 ALM Tools (4 days)
• Developers Training with Microsoft Visual Studio 2010 ALM Tools (4 days)
• Imaginet On Demand Online Web Training
– Scrum/Kanban
• Professional Scrum Foundations (PSF) (2 days)
• Professional Scrum Master (PSM) (2 days)
• Professional Scrum Developer (PSD) (5 days)
• Professional Scrum Master (PSM) Using Microsoft ALM (3 days)
• Accredited Core Kanban Using Microsoft ALM (3 days)
To register or for more information, please visit our website here:
http://www.imaginet.com/ or contact us: info@imaginet.com
30. TFS / Visual Studio 2012
Remaining Workshops & Webcasts:
• Lean, Kanban, and TFS
• December 3 (1:00-2:30pm CT)
• Approaches to Kanban with TFS
• December 6 (1:00-2:30pm CT)
• December 20 (1:00-2:30pm CT)
• Streamline Your Testing with Visual Studio 2012 Testing
Tools
• December 13 (1:00-2:30pm CT)
• Getting Started with Coded UI Testing: Building Your First
Automated Test
• December 17 (1:00-2:30pm CT)
31. ALM Planning & Implementation Services
ALM Planning Testing
• ALM Assessment & Envisioning Workshops • Manual Testing with Test Manager Quick
(3 or 5 days) Start (5 days)
• VS & TFS Migration Planning Workshop (5 • Visual Studio Testing Tools Quick Start (10
days) days)
• TFS Deployment Planning* (5 days) • Visual Studio Automated Testing Quick Start
• Visual SourceSafe to TFS Migration (5 days)
Planning* (3 Days) • Visual Studio Load Testing Quick Start (5 or
• Visual Studio Quality Tools Deployment 10 Days)
Planning* (5 days)
Builds
Upgrade • Automated Build & Release Management
• TFS 2010 Adoption Quick Start (5 or 10 Quick Start (5 days)
days) • Automated Build Center of Excellence (CoE)
• TFS 2012 Adoption Quick Start (5 or 10
days)
Database
• TFS 2010 Upgrade Quick Start (10 days)
• Visual Studio Database Tools Quick Start
• TFS 2012 Upgrade Quick Start (10 days) (10 days)
Remote Support Integrations
• Remote Support for TFS & Visual Studio • Team Foundation Server (TFS) & Project
Server Integration Quick Start (10 days)
Lab • TFS & Quality Center Integration/Migration
• Visual Studio Lab Management Quick Start Quick Start (10 days)
(10 days) Email us at:
32. Want to know more...?
Phone: 1-800-989-6022
Email: info@imaginet.com
Website: www.imaginet.com
Facebook: www.facebook.com/justimaginet
Twitter: www.twitter.com/justimaginet
Slideshare: www.slideshare.net/imaginet
Attend a Webinar: www.imaginet.com/webinars
Attend a Training Class: www.imaginet.com/training
Editor's Notes
Test Runner:Show Test Explorer windowBuild solutionRun all tests and review test runnerSet to compile on buildRebuild againxUnit and nUnit:Open External web tests and show xUnit / explain why not in runnerTools > Extensions & UpdatesSearch online for xUnitDownload / install / restartRepeat process for nUnitWait for a moment… Show failed testAdd fakes for FiberkamFibre.DAL in .TestsAdd a new test for EmployeesControllerTest
Developers check source code into TFS.When needed, a build is initiated. The build machine gets the code, compiles it, packages it, and runs build verification tests. The build spins up virtual test lab in based on a known configuration. The build process installs the latest build into the SkyTap test lab.The build manager verifies the installation in SkyTap.The build manager captures the current lab configuration in a snapshot, adds it to the library and notifies QA.The tester receives the build notification and a manifest of the requirements and bugs that are ready for verification.The tester instantiates the “snapshot” in their own private lab and tests the applications.The tester identifies a defect and captures the current lab environment in a “snapshot”.The tester files a bug report and includes a reference to the snapshot environment.The developer receives the bug report.A developer examines the bug report and instantiates their own copy of the lab environment at the exact point at which the tester reported the defect.Developer works with he lab environment to understand and fix the defect.Developer checks the fixes into version control for inclusion in a subsequent build.
Test Runner:Show Test Explorer windowBuild solutionRun all tests and review test runnerSet to compile on buildRebuild againxUnit and nUnit:Open External web tests and show xUnit / explain why not in runnerTools > Extensions & UpdatesSearch online for xUnitDownload / install / restartRepeat process for nUnitWait for a moment… Show failed testAdd fakes for FiberkamFibre.DAL in .TestsAdd a new test for EmployeesControllerTest