Just an FYI, the very structure of a KDT file is not going to play 100% nice with most version control systems out there. KDT files are a type of XML. Generally, that wouldn't be a problem. But because it's not standard coding structures and the tagging isn't always clear, version control systems' auto-merge capabilities don't always play nice.
Generally, as a rule of thumb, I suggest that, if you have a team of folks, don't have more than on person working on the same KDT file at the same time. Likewise, don't have them working on NameMapping updates at the same time.
As for sharing code on a drive... that's OK... but it's not ideal. Everytime one person clicks "Save" on the project, the other will get a message "Hey, the file updated. Want to refresh?"
All.
The.
Time.
If you DO need to have two people working on the same KDT at the same time, best thing to do is manually merge their steps within the TC editor and not use the auto-merge of your source control system.
Champion Level 2
tristaanogre wrote:
...
Everytime one person clicks "Save" on the project, the other will get a message "Hey, the file updated. Want to refresh?"
All.
The.
Time.
And note that TestComplete implements the 'last writer wins' strategy which means that:
-- If you agree to refresh you will lose the content of your local file;
-- If you refuse to refresh and save your file later, you will overwrite the file on the network share and the changes made by other person will be lost.
P.S. I do hope that SmartBear will implement the possibility to visually merge the content of of files to be refreshed so that the one who is refreshing can incorporate required changes from the changed file and not to lose the content of the local file.
Thanks tristaanogre
Really Appreciate your input.
We are avoiding working on a same KDT but sometimes it becomes hard in case team works on same KDT and there are merge conflicts.
