Object Identification approach

[sams001]

Hi,

In our project we use QTP's Object Repository for identifying the objects. In case of the object's property changes done by dev team, as its evident we need to make changes in OR to identify the objects correctly, which is not an easy task to manual tester who does not have knowledge abt QTP. Can we have something like storing the object property values required for identification in an xl and dynamically create the object during run time using Descriptive programming. With this in place, a manual tester also can modify the object's property values.

Is this a better solution? Pl suggest.

Thanks
Sams

[Ankesh]

It would increase the execution time. I would suggest you to maintain the OR smartly. In my experience I have not seen Dev changing the object properties so often. If they do, as a tester we have all rights to ask them to have atleast one property say, html id fixed.

[Ankesh]

Another approach would be to launch run the script in maintenance mode:

Maintenance Run Mode helps you maintain your Quick Test tests when your Application Under Test (AUT) changes. Maintenance Run Mode runs while QTP/UFT steps through your test. It points out where object recognition has failed, and then it helps you make the necessary changes to your script and Object Repository (O. R.). Maintenance Run Mode is like a magic little friend, or even a wizard helping you make sure your scripts always identify your objects correctly.

Maintenance Run Mode is especially useful when you receive the error message, “Cannot identify the object <<insert your object name here>>”. When you receive this error message, just launch into Maintenance Run Mode (and get those magnets ready!)