Multiple Checkout/Checkins from TestComplete with SVN Integration

Hi Sarma,



Files that compose TestComplete's project and project suite are described here: http://support.smartbear.com/viewarticle/56608/.

Generally speaking, the structure of the project is quite logical and you should be able to figure-out what files are expected to be changed when you change this or that in the project.

For example, if you add a new script unit to the project, script file and Script.tcScript file are expected to be changed. If you change some project setting, you should expect changes in the corresponding .mds file, etc.

The problem here, as I have said, is that those files are near to impossible to be merged even manually, so the only approach that will work with concurrent development is:

-- Think beforehand what you are going to change and what files this will influence;

-- Check-out and lock required files;

-- Make changes;

-- Check-in and unlock changed files.



Obviously, no one will be able to use this scheme in the real life during development.

I would suggest you to make an experiment: make two copies of the same project in separate folders; make different changes to them from TestComplete (or even logically the same ones, for example, add new project variable of the same name, type, etc.) and then try to compare the changes and consider: a) whether those changes can be correctly merged automatically; and b) how easy will be to correctly merge those changes manually. After this experiment you may re-consider my suggestion about dedicated person who makes manual merge in TestComplete's IDE and then submits changed test suite into the source code control system.