Bridging the Gap Between Developers and Testers Using Visual Studio 2010: Part 10 of 13 - Testing in the Lab

  • Article

 

VS-One-on-One---Bridging-The-Gap_thu[1]_thumb[4]

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
Part 6 of 13 – Bridging the Gap
Part 7 of 13 – Stop, We Have a Problem!
Part 8 of 13 – Let’s Get Back On Track
Part 9 of 13 – Multi-Environment Testing
Part 10 of 13 – Testing in the Lab (This Post)

In this session of our conversation, Bridging The Gap Between Developers and Testers Using Visual Studio 2010, Etienne and Vincent deploy the web service to the lab environment and then run tests against it to ensure that everything is working. During the Q&A session, Etienne answers a very important question: “We have test plan, test suite, work items, and builds. How do they all tie together?” He explains:

  • The plan is the overarching container that holds test suites that are composed of test cases.
  • Each suite is associated with a requirement – all test cases within the test suite are used to test the one requirement to which the suite is assigned.
  • The build is assigned to the plan – the build is created in order to test everything in the test plan. With each new build, all of the test suites would be rerun to ensure that they all still work.

With that, Etienne and Vincent, back to you.

For more information on the topics covered in this session, check out the following resources:

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.