Working More than one people on same Project?

Hello Krushna,

Please see the following topic to know how to organize the parallel development of a project: - Teamwork.



Regards, Artem

The help file gives some idea. But I have following doubts which is not clear



1- How the name mapping works in shared mode? If one user adds new component to the mapping, how it will be reflected?



2- Do we need to install multiple instance of Test Complete Software on all machines that is to be used for same project work? How the licence cost etc will be in this case.



3- Is using a source control is must for team work?



4- Is SVN supported in Test Complete as a source control tool?

Hello Krushna,

>>1- How the name mapping works in shared mode? If one user adds new component to the mapping, how it will be reflected?



The Name mapping item is copied to a local machine upon opening a shared project. Once it is opened, it is no longer kept synchronized. Thus, when one of users adds a new name mapping component to his project, he needs to distribute the modified NM scheme to the other users. This can be done manually (by recopying the modified NameMapping.tcNM file from the shared folder), automatically (by getting the most recent version from the source control system) and by [url= http://smartbear.com/support/viewarticle/12454/]merging the name mapping files[/url].



>>2- Do we need to install multiple instance of Test Complete Software on all machines that is to be used for same project work? How the license cost etc will be in this case.



Once you need to modify a test project from any of the machines working in team, you should have TestComplete installed on each of them. If you need to run a pre-prepared test project on multiple machines, you may have TestComplete installed on one of the machines and TestExecute installed on the rest of them.  Thus, the overall cost of the license could range from 1999$ to 4499$ multiplied by the Number of machines. See [url= http://smartbear.com/products/qa-tools/automated-testing/difference-between-licenses/]Difference Between Node-Locked and Floating User Licenses[/url].



>>3- Is using a source control is must for team work?



No. Source control systems are not obligatory (yet, desirable) for team work. TestComplete projects and project suites can reside in a shared folder. However, working with networked projects could require additional efforts from your team. For instance, solving the problem of concurrent attempts to edit the project (though, source control systems have built-in means to handle such situations).



>>4- Is SVN supported in Test Complete as a source control tool?



TestComplete supports source controls that are compatible with Microsoft Source Code Control API (MSSCCI). By default, SVN is not compatible with this API. However, there are plug-in wrappers like AgentSVN, or PushOK SVN which provide compatibility. Some of our users apply successfully these wrappers to work with TestComplete projects via SVN.



Best regards.