Automating steps in creating shared object repository?
We are attempting to create a shared object repository for our project, and would like to have UFT automate some of the work involved. However, whenever UFT is running, the object repository becomes read-only; changes made using SetTOProperty disappear when the test finishes. Is there a way to keep the repository readable?
The main purpose of SetTOProperty is to modify the properties during run time only not to update the Object Repository. You can modify the property and utilize to find some objects during run time for controls having dynamic properties.
Thank/Like to help others if my input helped you !!!
I am speaking for myself, not for my employer nor any one.
To do what you are looking to do you would have to use a non-UFT based repository such as a DB, Excel, XML etc.
I personally wouldn't even try to automated the editing of a shared OR (or any OR for that matter) - the potential for serious problems is risky. There is the built-in OR editor tools which is remarkably easy to use if you wish to merge, edit, modify or otherwise manipulate ORs. I'd personally recommend using that and not trying to automate the creation or editing of a share repository.
Also, as mentioned above, SetTOProperty will not permanently modify your existing ORs; it's used to change object properties during a script run so any property modifications are done in memory, not on disk, and will not be directly saved.