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
I'd be interested in this as well. We were originally going to have multiple test designers, but the name mapping issue quickly became troublesome and we went with a single designer. We were hoping that the talk about changes with namemapping in 10.4 (I believe) would resolve the problem. It would be disheartening to find out the problem with merging namemapping files still exists.
We have more test than a single designer can maintain and were sold that TestComplete supported this. We are using 10.5 and not 100% convinced it's a problem with TestComplete but seems to be.
My understanding is it's more of an import than a merge so if changes were made on a centralized file server the designers would merge (import) from the server and all would current. Likeway, when changes are made on the designers desktop the reverse would apply. Is this how you understand it to work?
Our expectation was that it would work similarly to a code repository merge. When the merge is requested, new, unconflicting changes are imported, while conflicting changes require some reconcilliation. What we found was that because of the plumbing of the namemapping xml (GUIDs seem to be (at least occassionally) unique to the machine that mapped the object), the same object mapped the same way but from 2 different machines resulted in either 2 mapped objects, or no mapped objects after a merge.
We have more than one (me) designer now, but most of the work is maintenance and not needing to map new objects. But in the near future we're going to have our QA team designing tests, so I hope the namemapping issue we ran into with 9.4 doesn't still exist in 10.5.
Our expectation was the same (code repository merge). When I looked further into the discrepancies multiple items were found with the same name and it used the first one found. We never had a screen appear which provided the option to resolve the discrepancies... only one which indicated a conflict. This doesn't work well for us.