Bridging the Gap Between Developers and Testers Using Visual Studio 2010: Part 5 of 13 - Tester at Work
![VS-One-on-One---Bridging-The-Gap_thu[1]](https://msdntnarchive.z22.web.core.windows.net/media/MSDNBlogsFS/prod.evol.blogs.msdn.com/CommunityServer.Blogs.Components.WeblogFiles/00/00/01/43/73/metablogapi/7563.VS-One-on-One---Bridging-The-Gap_thu1_0D543F8A.jpg "VS-One-on-One---Bridging-The-Gap_thu[1]")
In this post, we’re continuing our One on One with Visual Studio conversation from March 13 with Canadian MVPs Etienne Tremblay and Vincent Grondin, Bridging the Gap Between Developers and Testers Using Visual Studio 2010 . If you’ve just joined us, the conversation builds on the previous posts, so check those out (links below) and then join us back here. If you’re re-joining us, welcome back!
Bridging the Gap Between Developers and Testers Using Visual Studio 2010
Introduction
Part 1 of 13 – Migrating VSS to TFS
Part 2 of 13 – Automating the Build
Part 3 of 13 – Where’s Our Backlog?
Part 4 of 13 – Adding a Tester to the Team
Part 5 of 13 – Tester at Work (This Post)
In this session of our conversation, Bridging The Gap Between Developers and Testers Using Visual Studio 2010, Etienne and Vincent explore the many different facets of manual testing. First, they introduce us to the different types of tests that can be run with Test Manager and walkthrough creating a test case that runs against the application. Once the test case is designed, Etienne and Vincent show us how to run the test case, record the actions for each step as the test case is being executed, and then explore the results of the test and the information Test Runner captures. All of that information is then used to create a new bug that is then filed for the developers. Etienne also highlights different settings that can be enabled or disabled for each test, including video recording and IntelliTrace.
During the session, Etienne and Vincent highlight a few cool tips and ticks including:
- Copying and pasting steps into the test case rather than typing them out
- Shared steps to avoid having to re-enter the same steps in multiple test cases
- Using the screen capture feature of Test Runner to include images with test results
With that, Etienne and Vincent, back to you.
For more information on the topics covered in this session, check out the following resources:
- Testing the Application
- Running Manual Tests Using Test Runner
- Share Common Test Case Steps Using Shared Steps
- Create Test Settings for Manual Testing
- Capture a Screenshot While Running a Test
- Collect IntelliTrace Data to Help Debug Difficult Issues
- Record a Video of Your Desktop as You Run Tests Using Test Settings
Remember, this conversation is bidirectional. 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.