Can anyone explain to me how the shared repository functions. I have a web app that I have maybe 3 tests that I run on one page. Now, in theory these test use some of the same objects but when I record the tests the objects are recorded repeatedly. So, I have multiple versions of the objects, and no sharing. What exactly am I missing? How do you approach the management of this repository. Any insight would be greatly appreciated.
Thanks for the advice. I wish the manual could tell us more. I did read the chapter you mentioned but find the problem more to do with the management of the repository. I understnad the concepts. What I dont understand is the initial set up and maintenance issues. For example, within a frame on a web page I have 6 different functionalities to test (buttons that open dialogue boxes)now I would have thought that the frame would be recorded as a seperate object and then the different functions within that frame to be recorded as children. As it is the functions are recorded like this in the object repository:
I would like to the OR to be more like Frame>button_1, button_2, button_3 etc
So If a change is made to the frame, do I have to then make subsequent changes to each frame object? Thats how it seems at the moment.
Ok, thanks for the advice, that has actually solved another problem I was having. The problem I detailed above is not exactly how I thought. I basically had not investigated deeply enough into what each frame element was relating to. Now I now that they are actually named differently. Sorry to have included this I was a little confused with the object repository.