1. 07 | Integrate Development and Operations Anthony Borton | ALM Consultant, Enhance ALM Steven Borg | Co-founder & Strategist, Northwest Cadence

2. Implement an automated deployment process Implement pre-production environments Manage feedback between development and operations Troubleshoot production issues Module Overview

3. Microsoft Virtual Academy Implement an automated deployment process

4. What the Study Guide says… architecting an automated build and deploy workflow integrating automated tests automating deployment into both test and production environments

5. Microsoft Virtual Academy Implement pre-production environments

6. What the Study Guide says… automating the creation of virtual test lab environments automating deployment into virtual test environments

7. What’s on a developers PC? LINQPad Web Platform installer DropBox Paint.NET TeamViewer PowerShell 7-Zip UltraMon Team Explorer Windows 8 Process Monitor Process Explorer XMLSpy SQL Complete TestDriven.NET Windows Live Writer Auto Hotkey Window Pad Fences Bins NuGet Microsoft Test Manager Visual Studio.NET Reflector Notepad 2 CodeRush Resharper Fiddler WinMerge Expresso FireBug NDepend WatiN StyleCop Pex {Censored} {Inappropriate}

8. What does Production look like? Server SOE Multiple servers Controlled patching Firewalls Server hardening scripts Load balancers

9. Lab Management Workflow BUILD restore env. DEPLOY take env. snapshot TEST

10. Two types of environments StandardSCVMM Automated deployment to environment Execution of manual and automated tests Automated data collection Startup and shutdown of virtual machines  Use of Snapshots to revert to different states  Support for Network isolation  Support for physical servers  Support for Hyper-V Support for VMWare 

11. Lab Environments A lab environment is a collection of virtual and physical machines, which you can use to develop and test applications. A lab environment can contain multiple roles needed to test multi-tiered applications, such as workstations, web servers, and database servers. You can use a build-deploy-test workflow with your lab environment to automate the process of building, deploying, and running automated tests on your application.

12. Benefits of Lab Environments Reduced time between build and when a tester can start testing You can use a test plan to run automated tests using Microsoft Test Manager You can use a build-deploy-test workflow to test multi-tiered applications automatically Collect diagnostic data from all machines, even during manual testing

13. Benefits of SCVMM Environments Quickly reproduce machine configurations − store collections of VMs that are configured to recreate typical production environments. Reproduce the exact conditions of a bug – When a test run fails, you can store a copy of the state of your lab environment. Run multiple copies of a lab environment at the same time – You can run multiple copies of your lab environment at the same time without conflicts.

14. Supported OSes for Virtual Machines Windows XP SP3 and later versions Windows Vista Windows Server 2003 Windows Server 2008 Windows Server 2008 R2 Windows 8 or later versions

15. DEMO Microsoft Virtual Academy The Build-Deploy-Test workflow in action

16. Microsoft Virtual Academy Manage feedback between development and operations

17. What the Study Guide says… implementing tools to simplify communication identifying, measuring, and reporting key analytics and performance indicators such as cycle time and mean time to repair (MTTR) creating appropriate shared artefacts and process to facilitate communication standardizing required artefacts for defect reports creating strategies for test case reuse (both automated and manual) in production

18. The Microsoft System Center Family Configuration Manager Data Protection Manager EndPoint Protection Orchestrator Operations Manager Service Manager Virtual Machine Manager

19. Microsoft Virtual Academy Troubleshoot production issues

20. What the Study Guide says… gathering defect data from bugs in a production setting providing actionable data to the development team monitoring applications running in production for potential issues managing incident response times collaboratively between development and operations

21. A Common Problem Developers typically spend considerable time debugging code Often bugs are difficult to find and in many cases we simply can’t reproduce them Much time is wasted stepping line by line through code IntelliTrace is a feature in Visual Studio Ultimate that is designed to help with this scenario Find time Fix time

22. Concept Basic concept is “capture debugger state information during program execution” Think of it like a personal DVR for developers

23. Tester/Developer Scenario Tester captures IntelliTrace data while executing test cases..iTrace file is attached when the Tester raises a Bug Developers are able to find the issue much more quickly with the aid of the.iTrace file. Once fixed they mark the bug resolved so the tester can retest Tester Dev Team

24. Enabling the IntelliTrace Collector The tester will enable the IntelliTrace data collector in the Properties for the test plan

25. Collector Configuration The tester can configure the specific information that the data collector will collect

26. Raising a bug with the IntelliTrace log included When the tester creates a bug, the iTrace log file is automatically linked if the collector is enabled

27. Developers receive bug work item

28. Developers open the.iTrace file

29. The Importance of Symbol files Symbol Files –.PDB files –Used during the debugging process –Includes Source File Names, Line Numbers and Local Variable Names You should always keep your symbol files around Symbol Server –Central location for storing your PDB files –Essentially this is just a file share

30. Make sure you know the role of Lab Management and what it offers a team Run through various Build Definition settings for DefaultTemplate and LabDefaultTemplate processes Be familiar with the capabilities of each System Center product

31. ©2013 Microsoft Corporation. All rights reserved. Microsoft, Windows, Office, Azure, System Center, Dynamics and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.