|
| Customisation - Analysis of the custom component |
Customisation is needed if you want to change the statements the tool records for your custom object(s). The first step is to make sure that we are facing a custom control, and once it is identified as a custom control, that the custom control does not require only running user actions.
Three methods to identify custom objects:
|
WinRunner™ records obj_ statements e.g. obj_mouse_click 
|
WinRunner™ Spy shows component as Object 
|
WinRunner™ GUI Map stores the control as Object When you record on a custom object that is not supported by the appropriate add-in WinRunner™ creates a description based on the object's class and index (windows id, ordinal identifier, etc...). Because the dynamic assistive identifier (index, windows id, ordinal identifier, etc...) changes depending how the objects are currently laid out in a window (number of objects), the physical description containing this property is not consistent. This inconsistent description may lead to the tool being unable to identify the same object in between runs or even during a single application execution. 
|
| Close |