Hi all,we are having troubles with tc-projects under source control, using subversion and tortoise. So far we´ve used a workaroundusing a locking system so only one person at a time was able to alter the tc-project.The reason for this workaround was that we found it impossible to manually merge some of the tc-files. Unfortunately it is almost impossible not getting conflicted files if more than one person works on a tc-project.This is not satisfactory for us. There surely must be a proper way of doing this and ending up with lesser conflicts.greets and thanx for any ideas.Carsten

Hi Carsten,The current architecture of TestComplete project files does not assume they can be merged by third-party merging software. An expected way to work with TestComplete projects added to an SCC system is to lock a file if it is checked out by a user.

Hello David,thank You for Your answer. Until now we have followed Your advice and never at one time more than one developer workedon the tc-project.However, I find it hard to believe that there is no way to allow several users to work on one project at the same time?!What if the whole project is subdevided into various parts? Say for each user a seperate testproject in one solution?Would You be able to supply a detailed description of how to achieve what we desire?best regardsCarsten

Hello Carsten,In this case, each developer should work over his/her tests without touching any other tests. If the current work requires making modifications to project settings of other project files, these files should be checked out, modified, and then, checked in right after this.Please let me know if you face any specific problems working with TestComplete and its SCC integration feature.

Hello David,thanx for Your quick reply.We will try it out, and I´ll get back to You with what we have experienced.Carsten

HelloDavid,we have been trying.We are using Subversion and TortoiseSVN as source-control, this is notintegrated in TC. We are using TC with several Named User licenses.Every userhas his TC-project-Version on his own computer. The problem starts,when a usertries to update his version.Here a short description of how we tried to avoid conflicts:Developer1 (D1) opens TC-Project (tcp) and adds a keywordtest, checksin. Developer2(D2) opens same tcp and updates. No problem. D2 adds keywordtest andchecks in.D1 updates -> no problem.D1 changes his test, D2 changes his test. D1 checks in, D2 wants tochecks in.Now D2 wants to update his version and gets conflicts!!The conflicted file is the tcCfgExtender. We are not able to relate thechangesin that file to what has been changed in the individual tests.When D2 nowresolve the conflict by Choosing the Option “Taking theirs”, D2 has noproblemsto continue his work on his updated version.Is it possibleto take this file out of source-control or will that raise problems forusingTC?Please giveus some advice.greetingsCarsten

Having Trouble with tc-projects under source control

13 Replies

rminnich
Contributor
14 years ago
As David said in the first posts of this thread, all configuration files from TC project cannot be merged easily and reliably. That is why the recommended way for TestComplete is to organize the work in such a way that there is no need to work on the project concurrently.

Do you mean that testers should not work in the same test item in a project (script, keyword script), but using a shared project is fine?
Dmitry_Nikolaev
Staff
14 years ago

Hi Russell,

Yes, using a shared project is fine while two testers do not edit the same script or keyword test at a moment. When one of them changes a project item and saves it, the item is automatically updated for the second tester. If the second tester has this project item's editor opened at that moment, TestComplete notifies that the element has been changed and asks whether it should be reloaded.
aldebaran
Occasional Contributor
14 years ago
Hi Russell,

following David´s advice and setting svn.ignore to the files not listed in the List of Files Added to Source Code Control , we rarely have to try and resolve conflicts manually. Communication between test-team-members has to be internsive though. If person A needs to add a new keyword-test or script, an update is needed as usual, but all other team members must have committed their changes if they included adding of tests.

greets

c

Forum Discussion

Having Trouble with tc-projects under source control

13 Replies

Recent Discussions

I'm not able to handle cookie pop up with test complete using java script,I'm using windows machine.

Unable to install upgrade of TestComplete as previous installation not finished.

If statement

Related Content

Trouble Identifying controls on an Excel Form

Switch statement troubles!

Global variable trouble!