The document discusses best practices for software testing using Visual Studio Lab Management, highlighting the importance of actionable bug reporting and the integration of various tools for efficient testing. It emphasizes the need for developers to access test environments, manage build deployments, and utilize infrastructure features available since Visual Studio 2010. The presentation outlines strategies to improve testing processes, reduce inefficiencies, and capture detailed information for debugging and bug resolution.

1. Developer Day
Software Testen mit Visual Studio Lab
Management
Nico Orschel Marc Müller
MVP VS ALM, AIT Principal Consultant, 4tecture GmbH
Nico.Orschel@aitgmbh.de mmueller@4tecture.ch

2. Introduction 5’
Build, Deploy and Test 20’
Infrastructure 10’ Agenda
Lab Management for Devs 15’
Summary / Q&A 10’

3. Chapter 1/5
Introduction

4. You can’t fix
Testers find bugs but may be
unable to document them in
what you can’t
sufficient detail so that they can
be acted upon by developers.
reproduce .
“If it can’t happen twice, it didn’t
happen once” - James (my mechanic)
Developers may not have access to the only
environment in which a bug can be isolated.

5. Allow testers to create bugs that contain “actionable”
information.
Allow developers the ability to “Make it happen the
second time”
Give developers access to the test environment at the
point the bug was encountered.

6. Test Case (for
repro steps)
Screenshot
Video Capture
System Info
Debug Log
Test
Environment
Log
Action
Recording

7. Pre-Prod environment
Web Web DB
UAT Server Server Cluster Release
Manager
QA environment
Dev environment
Web DB
Web + DB
Server Server
Server
Build environment
Web DB
Server Server
Tester
Devs

8. Chapter 2/5
Build, Deploy, Test

9. build
applicati
on
deploy
run
applica
tests
tion

10. build
app.
restore
snapsh run restore
ot tests env.
take
env. deploy
snapsh app.
ot

12. Revert virtual environment to ‘clean’ baseline in
minutes than hours
Predictable (Web) deployment (using MSDeploy)
Post-deployment snapshot facilitates exploratory
testing

13. Chapter 3/5
Infrastructure

14. Available since Visual Studio 2010
Integrates with Hyper-V
Allows us to:

15. Team Foundation Server
(TFS) System Center Virtual
Lab Management Machine Manager
Test Case management
Hyper-V Hosts Library Shares
Build management
VM1 LS1
Work Item Tracking
VM2 LS2
Source Control VMn LSn
17

16. Team Foundation Server
System Center
Lab Management Virtual Machine Manager
Test
Test Case Management Controller
Build Management Hyper-V host Library Share
VM1 Stored Virtual
Source Control Machine
Lab agent
Work Item Tracking Test Agent Stored Virtual
Stored Virtual
Stored Virtual 2
Machine
Machine 2
Build Environment
Build agent
Controller
Client: Client:
Test Manager Visual Studio
Build agent for
Compilation

18. Chapter 4/5
VS Lab for Devs

20. Chapter 5/5
Summary

21. Microsoft® Visual Studio® 2012 Premium
OR
Microsoft® Visual Studio® Test Professional 2012

22. No more waiting for build setup
• Revert to a ‘known’ state in minutes
• Predictable multi-machine application deployment
• Know build quality before investing in further testing
No more wasteful testing
• Prioritize test cases based on code changes
No more no repro
• Environment snapshots, Intellitrace and other collectors capture exact state of problem

23. Allow Testers to capture bugs the first time they happen
Document the hell out of a bug so that even a Developer
can fix it
Use Rich Bug data (Intellitrace, Video, Action Logs,
Snapshot Environments) to find and fix the root cause
Create tests that prove the bug is gone

24. Contact
Nico Orschel
Nico.Orschel@aitgmbh.de
AIT GmbH & Co. KG
http://www.aitgmbh.de
http://www.tfsblog.de
http://www.xing.com/profile/Nico_Orschel
http://de.linkedin.com/pub/nico-orschel/25/484/602
Ihre Software effizienter entwickelt AIT GmbH & Co. KG, Leitzstr.AIT GmbH & Co. KG
© 45, 70469 Stuttgart