Best practice for people working on one solution

Ranorex Studio, Spy, Recorder, and Driver.
Posts: 1
Joined: Mon Nov 25, 2013 12:07 pm

Best practice for people working on one solution

Post by MarcelK » Mon Nov 25, 2013 12:51 pm


currently a team of 3 persons works on automatic tests for our online application. Everyone of them works on their own, but in the same Ranorex project. This has the advantage that every user has access to all modules and repositories. The complete solution with all Testcases is executed by a separate PC with Ranorex Runner installed on it. The huge disadvantage of this solution is, that we often run into subversion conflicts in the main project file, when two persons worked on tests at the same time.

I think that there are some possibilities to fix this problem, but I'm not sure which one to use. These are the things I thought about:
1. I could create different branches for each user. Ranorex Runner uses the root branch, while all tester develop their tests in there branch. Once a day, every user gets the last changes of the root branch and at the end of a day every user merges his changes into the root branch. The problem is, that reintegrating a branch and stuff like that, is more complex like just clicking the update button. And I am absolutely not sure, if this would even fix the problem or if it justs shifts the problem to the reintegration.

2. I create a new project for every user. I seems to be possible to open and link an existing repository and it also seems to be possible to add an existing item (i.e. folder) to my project. So every user could have its own project, but share the same modules and repositories. Eventually it is also possible to copy the new testcases to the "mother" project once a week. Does this work? Will both the added repository and the added item still 'update', if another user changes the module? Or is it just copied to the new subversion directory?

Are there any other possibilities to solve this problem? Which solution would you prefer?

User avatar
Support Team
Site Admin
Site Admin
Posts: 12145
Joined: Fri Jul 07, 2006 4:30 pm
Location: Houston, Texas, USA

Re: Best practice for people working on one solution

Post by Support Team » Wed Nov 27, 2013 4:57 pm

Hello Marcel,

It might be a good approach to use libraries within your team to minimize merge conflicts.
I would recommend to have a look at our blog Organizing a Test Automation Project.

Markus (T)