Managing Releases Between Your Development and QA Teams with Microsoft Visual Studio Team System 2008

Chris MenegayVP of ConsultingNotion Solutions, Inc.DTL319

Agenda

Review the problemDefine the goalsOverview of a possible solution

The ProblemThe development and test teams have built a wall

Development work happens on one side of the wallTesting happens on the otherBuilds and test results are passed back and forth, but not in a collaborative fashion

Development Perspective

Works on my machine!What build is being tested?How do I repro this?I already fixed this bug!The testers are clueless twits that don’t even know what good software is!

This is still broken? They said they fixed it!Do we have a new build?What’s supposedly fixed in this new build?Is the new build deployed to our QA environment?The developers are clueless twits that don’t even know what good software is!

Test Perspective

Typical Workflow

Version Control

Typical Workflow

Version Control

Build Process

Typical Workflow

Test Environment

Version Control

Build Process

Typical Workflow

Test Environment

Version Control

Build Process

Typical Workflow

Test Environment

Defect Tracking SystemTitle

DescriptionBuild version?Repro steps?What test case?What was the test environment like?

Breaking the Barrier

Common bug trackingConsistent and predictable build deploymentShared test casesReproducible test environment

Breaking the Barrier

Common bug trackingConsistent and predictable build deploymentShared test cases

TFS Build

Test cases and bugs

Code and bugs

DevelopmentCode

QACode

ProductionCode

Development

QA

Production

1.0 2.0

Branching, Building and Deploying in TFSChris MenegayVP of ConsultingNotion Solutions, Inc.

demo

Thing to Consider

Builds can do ALMOST anything!Review MSDeploy Creating installersSMS/System CenterUpgrades versus new installsConfig files

Build Considerations

Team Foundation Server

Build Considerations

Team Foundation Server Build

Process

Build Considerations

VM Lab

Team Foundation Server Build

Process

Build Considerations

VM Lab

Team Foundation Server Build

Process

Build Considerations

VM Lab

Team Foundation Server Build

Process

Test Considerations

VM Lab

Test Considerations

VM Lab

“Repro” Considerations

VM Lab

https://vlab.skytap.com/configurations/22528

Testing with a VM LabChris MenegayVP of ConsultingNotion Solutions, Inc.

demo

Other Benefits

VM Labs can be used for:Demos for customersMaintaining snapshots of old versionsProduction hot-fixes Tech writer access for screenshotsTesting CI builds using GUI automationLoad testing

Circling Back

Creating installersUpgrades versus new installsConfig files

Installers

Setup and Deployment projectsNot MSBuild compatible

InstallShieldWiseWIX!

Upgrades

Blow away the bits!Upgrade the database

Look at Visual Studio Team System 2008 Database Edition

Creates upgrade scripts for youCan be integrated into Team BuildBe sure to use GDR or GDR2!

Config Files

Different for Dev/QA/ProdSome options:

3 configs in one branch, let build pick the right oneDifferent configs - one in each branch

SummaryCan’t we all just get along???

www.microsoft.com/teched

Sessions On-Demand & Community

http://microsoft.com/technet

Resources for IT Professionals

http://microsoft.com/msdn

Resources for Developers

www.microsoft.com/learningMicrosoft Certification and Training Resources

www.microsoft.com/learning

Microsoft Certification & Training Resources

Resources

Track Resources

Visit the DPR TLC for a chance to win a copy of Visual Studio Team Suite. Daily drawing occurs every day in the TLC at 4:15pm. Stop by for a raffle tickethttp://www.microsoft.com/visualstudio http://www.microsoft.com/visualstudio/en-us/products/teamsystem/default.mspxPlease visit us in the TLC blue area

Complete an evaluation on CommNet and enter to win!

question & answer

© 2009 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista 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.