Is it practical to share a project between testers without Source Control

Question

I have just started sharing my network TC project with another tester. We have both noticed that numerous warning messages pop-up about files (.mds for example) needing reloading. This happens eventhough we have been careful to not update the same file simultaneously. Also I have had TestComplete go into a temporary frozen/not-responding state about four or five times a day since we started sharing the project.

So which, if any, of the following are true?

- What I have described is normal. We should ignore the problems described above and just carry on.

- We are mad not to use source control.

- We don't need to use source control, but the above problems should not be occurring.

Any suggestions gratefully received.

Thanks, Jim

hpdvs2 · Answer

Option B: We are mad not to use source control.&nbsp; :DFor your case, I would recommend Perforce.&nbsp; (I don't use it now, as I have TFS 2010, but it was good in the past)It comes with 2 free seat licenses. and was easy to setup.&nbsp; However, go with any version control you are comfortable with.Essentially, since you have it shared, you are also facing the risk of accidental deletion, from two sources, Source code can change with no clear idea of who did it, locked files, as well as the various issues you listed above.&nbsp; Though I'm sure you have a backup anyway, if not, this will give you another location to do this from.Another options is DropBox, of SkyDrive, which is sort of like a shared drive, but everytime that you save, it copies the changes onto a server, and then onto any other systems paying attention.&nbsp; It works pretty well, and should prevent file locks.&nbsp; They also have file Versioning or backup&nbsp;as a paid option, but otherwise they are free upto 2 gigs.Typically, you can both operate with full editing rights, then do a diff to see what changes were in.This will also give you your version control, and a separate backup.

alevans4 · Answer

I often run into the MDS issue you are describing when different installations of TestComplete have different extensions installed.&nbsp; TestComplete stores some information about extensions in the MDS file and if you share that file between two boxes with different extension setups, you will clobber the MDS file every time.&nbsp; It's a dumb thing I wish SmartBear would fix.

jimsmith_1 · Answer

Dan, you use TFS 2010 for source control?We have TFS 2010 here and about a year ago I tried to use the source control on a TC project suite. I remember spending several hours individually checking in every separate file in the project suite when I first set it up. Also when closing the project suite at the end of a working session there seemed to be an awful lot of checking in (every new visualizer image as I recall)&nbsp;and worrying error messages.Do you find using TFS 2010 for TC source control OK?

alevans4 · Answer

We actually use Visual SourceSafe (I know, I know).&nbsp; Once I got all the different installations of TestComplete using the same set of extensions, I had no further problems.

jimsmith_1 · Answer

Bert,I've not thought about TC extensions before. Are those the items shown in the FILE &gt; INSTALL EXTENSIONS window? To avoid the .mds warning messages, do I need to make sure that all TC users have the same extensions listed, or the same extensions active?Thanks, Jim

Forum Discussion

Is it practical to share a project between testers without Source Control

Recent Discussions

Process "crashed" and test fails when closing the application in test

Name mapping gone

TestComplete: Connect to Azure Cosmos DB

Related Content

TestComplete Best Practices

Best Practices using ReadyAPI

Best practices for automation