Software Testing with Visual Studio 2010 (Microsoft Windows Development Series)
Jeff Levinson
Language: English
Pages: 336
ISBN: 0321734483
Format: PDF / Kindle (mobi) / ePub
Use Visual Studio 2010’s Breakthrough Testing Tools to Improve Quality Throughout the Entire Software Lifecycle
Together, Visual Studio 2010 Ultimate, Visual Studio Test Professional 2010, Lab Management 2010, and Team Foundation Server offer Microsoft developers the most sophisticated, well-integrated testing solution they’ve ever had. Now, Microsoft MVP and VS testing guru Jeff Levinson shows exactly how to use Microsoft’s new tools to save time, reduce costs, and improve quality throughout the entire development lifecycle.
Jeff demonstrates how Microsoft’s new tools can help you finally overcome long-standing communication, coordination, and management challenges. You’ll discover how to perform first-rate functional testing; quickly create and execute tests and record the results with log files and video; and create bugs directly from tests, ensuring reproducibility and eliminating wasted time. Levinson offers in-depth coverage of Microsoft’s powerful new testing metrics, helping you ensure traceability all the way from requirements through finished software.
Coverage includes
• Planning your tests using Microsoft Test Manager (MTM)
• Creating test settings, structuring test cases, and managing the testing process
• Executing manual tests with Microsoft Test Manager and Test Runner
• Filing and resolving bugs, and customizing your bug reporting process
• Automating test cases and linking automated tests with requirements
• Executing automated test cases through both Visual Studio and Microsoft Test Manager
• Integrating automated testing into the build process
• Using Microsoft’s Lab Management virtualization platform to test applications, snapshot environments, and reproduce bugs
• Implementing detailed metrics for evaluating quality and identifying improvements
Whether you’re a developer, tester, manager, or analyst, this book can help you significantly improve the way you work and the results you deliver—both as an individual right now, and as a team member throughout your entire project.
herein. The publisher offers excellent discounts on this book when ordered in quantity for bulk purchases or special sales, which may include electronic versions and/or custom covers and content particular to your business, training goals, marketing focus, and branding interests. For more information, please contact: U.S. Corporate and Government Sales (800) 382-3419 corpsales@pearsontechgroup.com For sales outside the United States, please contact: International Sales international@pearson.com
or fail a step, Test Runner automatically moves you to the next step. If you choose not to pass or fail a step, you must manually move to the next step in the Test Case. There are no negative effects for not passing or failing a step with no validation. Figure 4-12 shows the second of the three tests executing that contains the set of Shared Steps. Figure 4-12: Shared Step execution In the first panel, the Shared Step is listed as a collapsed, single step with a green option drop-down next to
bug get in the code? The default values are Unknown, Coding Error, Communication Error, Design Error, and Specification Error. Symptom How was this bug manifesting itself? (The screen didn’t complete a redraw, the data was incorrect, and so on.) This is a free form field. Triage Where is the team in the triage process? The default values are Pending, Info Received, More Info, and Triaged. The questions are, “What do you do about these differences?” and “Are they important?” Answering the
Chapter 5, “Resolving Bugs”—When you file a bug, the process and lifecycle of the bug is critical to reducing rework and driving reporting. This chapter discusses the Bug work item type, some customizations you might want to make to it, and how it serves as a communication mechanism for testers and developers. You are also introduced to how developers can use the Bug work item type to fix software correctly the first time and then how testers can verify that fix. This chapter introduces Test Impact
concludes with the technical capabilities of the Microsoft Visual Studio 2010 and Microsoft Test Professional 2010 tools and how they fit into the software development process. HIS CHAPTER ANSWERS SOME Software Testing Challenges I recently started working with a company and was discussing some of the issues the group manager was facing. I remarked that the software did not seem to be tested. He asked what led me to this conclusion. The answer was an apparent lack of testers, lack of