what's the best solution for working as a team on a TestComplete project?

Question

Hi&nbsp;Can someone please tell us what's the best solution to be used for working as a team on the same Testcomplete project? If the project is added to Source Control (TFS),&nbsp;i noticed that Stores should be checked out by a user on each checkpoint add for example. So it's not about checking out only the files a user is working on, because a test or a script will use other folders like Stores and TestedApp...&nbsp;So what can we do if we are more than 5 users and need to work on the same project at the same time?&nbsp;Please advise&nbsp;Thanks a lot.

alexkaras · Answer

Hi,
&nbsp;
The best way was suggested in the first referenced thread :) : try to avoid merging by all means. There are a lot of cases when automated merging can work incorrectly and manual merging is a real hell.
So, the less merging, the more stable, controllable and predictable your test code and project structure are.

shankar_r · Answer

Kind of same threat has been discussed in following threads, worth to take a look
&nbsp;
https://community.smartbear.com/t5/TestComplete-General-Discussions/Managing-Test-Complete-project-in-GIT/td-p/136956
https://community.smartbear.com/t5/TestComplete-General-Discussions/TestComplete-integration-with-source-control/td-p/87319
https://community.smartbear.com/t5/TestComplete-Functional-Web/Integration-with-TFS-Source-Control/m-p/72967#M13155
https://community.smartbear.com/t5/TestComplete-General-Discussions/Integration-with-GIT/td-p/91730
&nbsp;
Ref:&nbsp;https://community.smartbear.com/t5/TestComplete-General-Discussions/Integration-with-GIT/td-p/91730

shankar_r · Answer

I personally prefer GIT since it has easy way of doing many hard things.

alexkaras · Answer

Hi,
&nbsp;
&gt; The problem that Stores and TestedApp parts of the project should be checked out by each user on each change!
Yes, correct.
This can be handled by the locking version control system (like Visual Source Safe). In this case only one user at a time will be allowed to check-out the file. And it should be a requirement to check-in the changed file the sooner the changes were done the better.
In case of non-locking version control systems (git, svn, cvs, ...) it should be test developers' responsibility to establish and follow the process like this:
-- Update sources often;
-- Update sources right before the change to some project configuration file (Stores, Script, .mds file, ...) is going to be done;
-- Implement required changes as quickly as possible (add test item, add/change project variable, add script unit, ...);
-- Save changes to the project;
-- Commit changes to the version control system to make them available for all other colleagues (in case of git it is a good idea to push changes to the central repository);
-- Continue with changes to the content of script units or keyword test file that this given user is responsible for.
&nbsp;
Yes, this requires careful consideration and ahead actions planning, but this is the only real way to keep test project in a stable state with the minimal risk of losing changes made by whole team.
&nbsp;

habhoub · Answer

OK i checked them, but what i want to know is what's the best way between the provided solutions? Is there any preferred one?

Forum Discussion

what's the best solution for working as a team on a TestComplete project?

9 Replies

Related Content

Solution Script to Cleanup of Custom property values in the project

TestComplete with Zephyr Scale

TestComplete with Zephyr Scale

Tired of broken links to solutions existing in the answers to questions.

Type Mismatch Error solution?

Recent Discussions

testcomplete feature Intelligent Quality Add Ons

SessionCreator /Timeout option not firing EventControl_OnTimeout

Object Browser does not display WPF DataGridCell Border

Issue with retrieving text from listbox items in desktop win32 application

Read data from Excel