Design for continues testing & working in teams
Posted: Thu May 26, 2011 5:47 pm
hi
I am in the process of setting up Ranorex testing for a very big Flex App
using Jenkins to compile, deploy and run the end-to-end tests and subversion to manage the code.
For performance and development reasons, we will have separate jenkins jobs which start separate executable Ranorex compilations.
I plan having separate solutions which share two projects (libs, repo) which are part of a "master" solution. The libs Project will contain code modules to interact with the GUI, repo will contain a central items-repository only.
I see several challenges:
How to use a shared repository in a team setup where two to five people work on the same repo..
Does anybody do that already? If so, how to avoid conflicts and manage/structure the repo for the future? I'd like to have every gui element only once for better maintainability
Inputs are very much appreciated!
Thanks,
Christian
I am in the process of setting up Ranorex testing for a very big Flex App
using Jenkins to compile, deploy and run the end-to-end tests and subversion to manage the code.
For performance and development reasons, we will have separate jenkins jobs which start separate executable Ranorex compilations.
I plan having separate solutions which share two projects (libs, repo) which are part of a "master" solution. The libs Project will contain code modules to interact with the GUI, repo will contain a central items-repository only.
I see several challenges:
How to use a shared repository in a team setup where two to five people work on the same repo..
Does anybody do that already? If so, how to avoid conflicts and manage/structure the repo for the future? I'd like to have every gui element only once for better maintainability
Inputs are very much appreciated!
Thanks,
Christian