Bridging the Gap Between Developers and Testers Using Visual Studio 2010: Part 8 of 13 - Let’s Get Back On Track
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
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
In this session of our conversation, Bridging The Gap Between Developers and Testers Using Visual Studio 2010, Vincent updates the code to fix the production bug. Once fixed, he shows us how he associates the changes with the bug and commits the changes. Etienne then creates and runs a test case to prove that the bug has been resolved. Vincent highlights an important point – the new feature that he added is not in the build that Etienne is testing. Why? Etienne is testing the build from the code in the branch that was created for the production release (Vincent’s feature was not part of the production release). Etienne then merges the release branch with main branch to bring the bug fix in with the new features developed after the production release.
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.