Bridging the Gap Between Developers and Testers Using Visual Studio 2010: Part 7 of 13 - Stop, We Have A Problem!
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! (This Post)
In this session of our conversation, Bridging The Gap Between Developers and Testers Using Visual Studio 2010, Etienne and Vincent work through a situation that we are all very familiar with – a bug in production code! But how do we deal with defects in code after modifications have been made in support of new features? Branch the code. Etienne and Vincent explore the concept of branching and then show us how to branch code in a project.
With that, Etienne and Vincent, back to you.
For more information on the topics covered in this session, check out the following resources:
- Defining Your Branching and Merging Strategy (Originally written for Visual Studio 2005 Team Foundation Server, but the concepts still apply)
- Visual Studio TFS Branching Guide 2010
- Visual Studio TFS Branching and Merging Guidance (from MSDN Magazine February 2011)
- Clone Build Power Tool (Download)
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.