1. 28. Januar, Zürich-Oerlikon

2. Working with Virtual Test Environments Marc Müller Principal Consultant 4tecture GmbH

3. Agenda Introduction Build, Deploy, Test Infrastructure Lab Management for Developers Summary

4. Introduction Kapitel 1/5

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

6. So how do we make bug’s reproducible? 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.

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

8. Where do you test? Devs Tester UAT Release Manager Pre-Prod environment Web Server DB Cluster Build environment Web Server DB Server Dev environment Web + DB Server QA environment Web Server DB Server Web Server DB Cluster Web Server

9. Virtual Test Environments Test multiple configurations in parallel Lower Hardware / Software costs Easy preparation and clean-up of test environments Templates Initial and deployed-state snap-shots Link environment to bug Environment to reproduce bug (link to snap-shot) Multi-Machine Environments Snap-shots across multiple VM Network Isolation (fixed IP and Names, Custom AD, etc.) Single Tool – Microsoft Test Manager (MTM) Environment Management, Environment Viewer (no need for RDP Client), Test Mgmt, manual Testing

10. Build, Deploy, Test Kapitel 2/5

11. Traditional Build workflow build applicati on deploy applica tion run tests

12. Lab Management Build Workflow build app. restore env. deploy app. take env. snapsh ot run tests restore snapshot

13. Infrastructure Kapitel 3/5

14. Lab Management - Virtualization Available since Visual Studio 2010 Integrates with Hyper-V Allows us to: Create virtual machines from library Deploy virtual machines to host and group into an environment Snapshot of environment for rich bugs Save environment back into environment Deploy environment from environment

15. Lab Management – Non Hyper-V What about physical or non-Hyper-V Environments - Standard Environment now supports BDT Workflow - No snap-shot functionality - Workflow may be modified

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

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

18. Physical Machine Architecture – Standard Environment Team Foundation Server Lab Management Test Case Management Build Management Source Control Work Item Tracking Client: Test Manager Client: Visual Studio Test Controller Build Controller Test Agent Build agent for Compilation

19. DEMO LAB MANAEMENT WORKFLOW

20. Recap – Lab Management Workflow Revert virtual environment to ‘clean’ baseline in minutes than hours Predictable deployment Post-deployment snapshot facilitates exploratory testing

21. Network Fencing iis db 10.10.1.510.10.1.6 copy 1 iis db 10.10.1.510.10.1.6 copy 2  What is it?  create multiple copies of environment  they can run in parallel without conflicts  no application reconfiguration  How does it work?  internal fence network is created for all vms  a vm gets the same mac & ip address, and computer name in all copies  vms are also connected to the external lab network

22. Network Fencing iis db 10.10.1.510.10.1.6 172.22.48.15172.22.48.16 copy 1 iis db 10.10.1.510.10.1.6 copy 2 fence network (internal) lab network (external) 172.22.48.18172.22.48.17  What is it?  create multiple copies of environment  they can run in parallel without conflicts  no application reconfiguration  How does it work?  internal fence network is created for all vms  a vm gets the same mac & ip address, and computer name in all copies  vms are also connected to the external lab network

23. DEMO – STANDARD ENVIRONMENT

24. Lab Management for Devs Kapitel 4/5

25. DEMO - LAB FOR DEVS

26. Demo – Virtual Environment Recap Debugging with IntelliTrace locally Ability to create environments quickly Lab environment is a first-class entity Rich bugs with lab environments No more No Repro Snap-shot to debug Developer easily connects to environment

27. Summary Kapitel 5/5

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

29. If it happened once and you documented it, it doesn’t have to happen again! 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

30. Besten Dank für Ihre Aufmerksamkeit Für allfällige Fragen stehen wir Ihnen jederzeit gerne zur Verfügung: