View
224
Download
2
Category
Tags:
Preview:
Citation preview
Microsoft Visual Studio Team System: Software Diagnostics and Quality for Services Habib Heydarian
Lead Program Manager Microsoft Corporation
Justin MarksProgram ManagerMicrosoft Corporation
TL03
AgendaWhat are you going to hear?
The BIG Picture! Pushing Quality Upstream
Bug Prevention Reducing Cost Downstream
Bug Capture and Analysis
The BIG Picture!
Development
Test
Release
Software Phase
Cost of Bugs
Push Quality Upstream
Development
Test
Release
Software Phase
Cost of Bugs
What did I just break?
Impact Analysis: How It Works
Test Results
TFS
Tests->Method mapping
Build Drop SiteBuild
Visual Studio
void M() {}
void M() {
i++;}
Impacted Tests
The one line change!
What code have I changed?
What is the shortcut key to restart the Debugger?
CTRL + SHIFT + F5
Trivia
Reduce Cost Downstream
Development
Test
Release
Software Phase
Cost of Bugs
The Current World of Debugging How do developers debug software?
Break…Inspect…Step… Restart the application
multiple times Little insight into
reproduction environments
Lots of time spent pinpointing where the problem occurs
Introducing the Historical Debugger
Historical Debugging – How It Works
Collection Plan
Specifies the what and how of instrumentation
Instrumentation & Hidden Trace Points
Inserted into user’s code and the .NET framework using ICorProfiling APIs
User Experience• V
isualization of collected data integrated with the VS Debugger IDE
Development in a Team EnvironmentHow Can we Improve our Relationship with the Test Org? “Ping-Pong” effect
between dev and test team
Test spends a lot of time Gathering additional
information requested Reproducing Problems
Dev doesn’t have the proper environments to reproduce issues
Bridging the Gap Between Test and Development
Summary: The BIG Picture
Development
Test
Release
Software Phase
Cost of Bugs
VSTS 2010 Hands on LabsHOL Code Title
TLHOL07 VSTS 2010: Project Planning, Management, and Design
TLHOL08 VSTS 2010: Architecture Tools
TLHOL09 VSTS 2010: Team Foundation Server
TLHOL10 VSTS 2010: Software Quality
TLHOL11 VSTS 2010: Diagnostics and Performance
Related SessionsSession Title Speaker Day Time Location
TL47 Visual Studio Team System: A Lap Around VSTS 2010 Cameron Skinner 10/27 11:00 AM – 12:15PM Room 153
TL52 Team Foundation Server 2010: Cool New Features Brian Harry 10/27 03:30 PM – 04:45 PM Room 151
TL03 Microsoft Visual Studio Team System: Software Diagnostics and Quality for Services
Habib Heydarian; Justin Marks
10/27 03:30 PM – 04:45 PM Room 515A
TL09 Agile Development with Microsoft Visual Studio Lori Lamkin; Sunder Raman
10/27 05:15 PM – 06:30 PM Room 502A
TL45 Microsoft Visual Studio Team System Database Edition: Overview
Gert Drapers 10/27 05:15 PM – 06:30 PM Room 501B
TL59 Visual Studio Debugger Tips & Tricks John Cunningham 10/28 12:45PM – 01:30 PM Room 409A
TL37 Microsoft Visual Studio Team System: Leveraging Virtualization to Improve Code Quality with Team Lab
Ram Cherala 10/29 12:00 PM – 12:45 PM Room 408B
TL61 Panel: The Future of Unit Testing Euan Garden, Jim Newkirk, Peter Provost, Nikolai Tillmann
10/29 12:00 PM – 12:45 PM Room 406A
TL60 Improving Code Quality with Code Analysis Ravs Kaur 10/29 12:00 PM – 12:45 PM Room 409A
TL24 Improving .NET Application Performance and Scalability
Steve Carroll;Ed Glas
10/29 01:15 PM – 02:30 PM Room 153
TL15 Architecture without Big Design Up Front Peter Provost 10/29 04:45 PM – 06:00 PM Room 403
TL04 Microsoft Visual Studio Team System Team Foundation Server: How We Use It at Microsoft
Stephanie Saad 10/30 08:30 AM : 9:45AM Room 151
TL51 Research: Contract Checking and Automated Test Generation with Pex
Mike BarnettNikolai Tillmann
10/30 08:30 AM : 9:45AM Room 403
Questions and AnswersThank You
© 2008 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.
Recommended