Forum Discussion
AlexKaras
11 years agoCommunity Hero
Hi Kevin,
The best approach to organize TestComplete test projects in any source code control (SCC) system is to duplicate project's structure from the disk.
http://support.smartbear.com/viewarticle/63445/?st=0 contains a good description and http://support.smartbear.com/viewarticle/56603/ contains a list of files that should be added to the SCC system.
Note, that concurrent development is not recommended for TestComplete and the best approach here is to have a dedicated person who manually merges changes provided by different team members. Try to search the sub-forums of the TestComplete one (http://smartbear.com/forums/) - there were several threads there about concurrent development in TestComplete.
Finally, if you have several test projects that use the same NameMapping, you may try the approach mentioned here: http://smartbear.com/forums/f81/t88858/NameMapping-file-sharing-one-possible-approac
The best approach to organize TestComplete test projects in any source code control (SCC) system is to duplicate project's structure from the disk.
http://support.smartbear.com/viewarticle/63445/?st=0 contains a good description and http://support.smartbear.com/viewarticle/56603/ contains a list of files that should be added to the SCC system.
Note, that concurrent development is not recommended for TestComplete and the best approach here is to have a dedicated person who manually merges changes provided by different team members. Try to search the sub-forums of the TestComplete one (http://smartbear.com/forums/) - there were several threads there about concurrent development in TestComplete.
Finally, if you have several test projects that use the same NameMapping, you may try the approach mentioned here: http://smartbear.com/forums/f81/t88858/NameMapping-file-sharing-one-possible-approac