1 / 21

Microsoft Visual Studio Team System: Software Diagnostics and Quality for Services

TL03. Microsoft Visual Studio Team System: Software Diagnostics and Quality for Services.  Habib Heydarian Lead Program Manager Microsoft Corporation.  Justin Marks Program Manager Microsoft Corporation.

marilu
Download Presentation

Microsoft Visual Studio Team System: Software Diagnostics and Quality for Services

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. TL03 Microsoft Visual Studio Team System: Software Diagnostics and Quality for Services  Habib Heydarian Lead Program Manager Microsoft Corporation  Justin Marks Program Manager Microsoft Corporation

  2. Please use this format when talking about FUTURE products, services or features. AgendaWhat are you going to hear? • The BIG Picture! • Pushing Quality Upstream • Bug Prevention • Reducing Cost Downstream • Bug Capture and Analysis

  3. The BIG Picture! Release Cost of Bugs Test Development Software Phase

  4. Push Quality Upstream Release Cost of Bugs Test Development Software Phase

  5. What did I just break?

  6. Impact Analysis: How It Works void M() { } Tests->Method mapping Test Results Impacted Tests void M() { i++; } Visual Studio TFS Build Build Drop Site

  7. The one line change!

  8. What code have I changed?

  9. Trivia What is the shortcut key to restart the Debugger? CTRL + SHIFT + F5

  10. Reduce Cost Downstream Release Cost of Bugs Test Development Software Phase

  11. Please use this format when talking about FUTURE products, services or features. 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

  12. Introducing the Historical Debugger

  13. Please use this format when talking about FUTURE products, services or features. Historical Debugging – How It Works

  14. Please use this format when talking about FUTURE products, services or features. 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

  15. Bridging the Gap Between Test and Development

  16. Summary: The BIG Picture Release Cost of Bugs Test Development Software Phase

  17. VSTS 2010 Hands on Labs

  18. Related Sessions

  19. Questions and AnswersThank You

  20. © 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.

More Related