Anshoo_Arora

 Profile Answers by Anshoo_Arora 

• Nov 30th, 2007

 

The shared repository is stored as a file that can be accessed with multiple tests. You can say that it "fosters" a team environment by having a shared repository used by multiple testers for the same application (in read-only mode though). So, multiple actions can use the objects that are stored in the shared repository. For example, if you have a shared repository and you would like to test the application on another machine, you can just use that shared repository (if it has all the necessary object properties) to test the application at hand without re-recording.

The second part of the question: You can also merge shared object repositories. However, when you do this, one of them will be the primary source and the other will be the secondary and they will both point to a third repository, the target repository. The first and the second repository might have some conflicting object properties which are "handled" in the target repository with the help of some preconfigurable rules. The repositories being merged will remain unchanged.

- Anshoo Arora

binitp

 Profile Answers by binitp Questions by binitp

• Dec 10th, 2007

 

Concept of Shared object repository is useful when you have multiple team members working on same module. To avoid copy of same objects in OR in all the test will unnnecessary increase the size of the test. Moreover, SOR will provide a standard way of adding your objects in the OR. You need to follow some standards while adding objects to the same OR, so that you can refrain from duplicating objects.

Merging of OR is required to make a single master SOR for the AUT by adding different ORs.

Thanks,
Binit