Bridging the Gap Between Developers and Testers Using Visual Studio 2010: Bridging The Gap
- Posted: Mar 21, 2011 at 8:42 PM
- 871 Views
Right click “Save as…”
In this first One on One with Visual Studio conversation, we’re joined by two of Canada’s experts on Visual Studio and ALM (application lifecycle management). Etienne Tremblay and Vincent Grondin will be talking to you about how Visual Studio’s extensive integrated tools make you more effective and efficient, allowing you to collaborate better with the rest of your project team. They’ll show you how testing tools like MS Test, IntelliTrace, and Coded UI make it easier for you to test, and test often, while not increasing your workload; about Team Foundation Server’s work item management and it facilitates better communication between you, the testers, project managers, and development managers; Team Foundation Server’s version control, lab management, and team build tools and how they can automate many of the manual tasks that you’re required to do today; and lastly, about Visual Studio Test Professional’s Test Manager and Test Runner so that you can do your part in reducing testing efforts and as a resut, faster time to market.
In this session of our conversation, Bridging The Gap Between Developers and Testers Using Visual Studio 2010, Etienne and Vincent show how the developer uses the information gathered by the tester within Visual
Studio to resolve a bug. Vincent explores the test results and shows us the output of the recording taken when Etienne, as a tester, was running his test. Remember the IntelliTrace test setting that was enabled? Vincent looks at the results of that IntelliTrace and debugs the code to find the exact line of code that caused the application to crash. Once he makes the required updates to the code, he checks in the code and associates the code check-in with the bug filed by Etienne in the previous session. Last but not least, he updates the bug status, which lets Etienne know that he has a new bug to test.
Etienne looks up the recommended tests for the particular bug and reruns the test to ensure that the bug is, in fact, fixed. The first time he runs through the test manually. The second time, he uses Test Runner’s action
playback capabilities to have Test Runner run through the test case, enter all the data, and capture the results, all on its own.
For more information, please see Bridging the Gap Between Developers and Testers Using Visual Studio 2010: Part 6 of 13 - Bridging the Gap on the Canadian Solution Developers' Blog.
Share your comments and feedback on our Ignite Your Coding LinkedIn discussion. Etienne, Vincent, and I will be monitoring the discussion and will be happy to hear from you.