Merging Name Mapping Across Machines
We recently "graduated" from a single test designer to having multiple designers on multiple machines and a dedicated test server. The project suite and project files are on the designer's local mach...
Forum Discussion
Here's what we worked out in order to keep everything straight.
The master copies of our tests reside in subversion. Each person working on tests checks out their own copy of the tests, works on those or adds new ones, and commits changes as needed. Those merges are handled automatically.
Name mapping is merged manually every few days. One person takes the new name mappings from all the others and merges them one at a time inside TestComplete and deals with any issues. Once that new master copy is created, then that one is committed in subversion and is then available for everyone to use.
For overnight testing, a separate copy of the whole project is retrieved from subversion and the tests are run from that copy. We don't include a test in the overnight run until the name mapping that it needs has been merged.
Does that help?
Hi,
I little bit different approach is to have dedicated person who must be contacted when the changes to NameMapping are required. This person, together with the change requestor, corrects master NameMapping file that than is spreaded among others.
The pros of this approach is that: a) there is no need for the NameMapping merging; and b) as the NameMapping is changed 'interactively', i.e. during direct communication between the change initiator and (hopefully) more experienced person, there is a chance that the changes to NameMapping (and Aliasing) are done in the most effective way (e.g. correct usage of project variables, conditional mapping, extended find functionality, etc.).
The cons of this approach is that there is a need to communicate with the 'NameMapping file master' who may be not accessible right at the moment (e.g. due to the different time zones).
