NameMapping File and Git Source Control
Hello -
We use Bitbucket and Git Bash for all of our source control needs. We just started a proof of concept with TestComplete for a desktop Java application and are trying to establish our best ...
Forum Discussion
Marsha_R
Champion Level 3
Champion Level 3Hi RileyMartinez, I'm a Community Hero too. :)
Really really really you can see that all the experts in this thread have said *DON'T* use your usual file source control process on the name mapping file. We are just trying to save you the pain that we have all been through when we tried it some other way and totally trashed the name mapping and had to start over again from scratch.
If you are going to continue this way anyway, just make sure you have backups of all the different versions of your name mapping for when you have to go back.
Also, you don't have to be stranded with one person handling the name mapping file. Make sure everyone can do it and switch it off once a month or something.
Hi Marsha_R,
Yes sorry, I should have mentioned you are Community Hero of equal stature haha. Giving what you're saying about this, would you recommend Option B?
Also, Option B is how I understood the explanation of how your team handles multiple contributors. Let me know if I got the details wrong there.
Thanks!
- Marsha_R
That's exactly it. LinoTadros is really right and one person should do the mapping, but with our team we were willing to take the risk of each person doing their own mapping. We choose a mutually good day to give all the mappings to one person and they merge and resolve conflicts with the TC tool. That copy is passed back to the team and we run our tests with it and adjustments are made if necessary. The new copy that works for everyone is then checked in. Any of us are capable of doing it, so we avoid problems with vacations and such.
Awesome—thank you for the clarification! How often would you say you run into issues when passing the merged NameMapping file back for testing?