Solved
Share Project with N developers
Hi There, Right now, in my team, we are 7 people working with TC with 7 separate projects, as we use tortoise svn and TC does not support it, we can't use only one project because of the test i...
- We used mercurial in a previous life. We did, also, experience similar headaches dealing with checking in MDS file, Script.tcScript files, etc.
How did we handle it? We slapped the wrist of the person who checked in a new script unit without checking in the Script.tcScript file. This was standard practice. The MDS file was not nearly as important. It gets updated on the fly, anyways, every time you run the application. The only one we really needed to worry about was the Script.tcScript file on a per project basis. You get that right, the rest of the script units fall into place just fine.
Now... NameMapping? Yeah, that gets iffy. Pretty much, if NameMapping needed to be updated, we had one person doing the updating and checking in the changes and then, once it was checked in, everyone did a "get new" on the file and used it as is. We pretty much locked that file down to limit it to one test developer to make sure we didn't step on each other's work.
