HI All,
In QTP 11 has added one more advanced feature Visual Relation Identifiers that will help to identify the objects with relation to other objects
You can now use visual relation identifiers to identify application objects based on other objects that are always near them.
This enables you to create a more reliable identification definition for test objects that are otherwise difficult to differentiate, and to ensure that the identification remains reliable even if the user interface design changes.
When testing applications with multiple identical objects, QuickTest assigns an ordinal identifier to each test object. This may lead to unreliable object identification. However, it may not (immediately) result in a failed step.
A visual relation identifier is a set of definitions that enable you to identify the object in the application according its neighboring objects in the application. You can select neighboring objects that will maintain the same relative location to your object, even if the user interface design changes. This enables you to help QuickTest identify similar objects much as a human tester would, and helps in creating more stable object repositories that can withstand predictable changes to the application’s user interface.
How Visual Relation Identifiers Work
NOTE : — > QuickTest uses visual relation identifiers only when one or more objects match the test object’s description properties during the identification process. If no objects in the application match the test object’s description properties, then the visual relation identifier you defined is ignored, and QuickTest continues to Smart Identification (if defined for that test object class).
In QTP 11 has added one more advanced feature Visual Relation Identifiers that will help to identify the objects with relation to other objects
You can now use visual relation identifiers to identify application objects based on other objects that are always near them.
This enables you to create a more reliable identification definition for test objects that are otherwise difficult to differentiate, and to ensure that the identification remains reliable even if the user interface design changes.
When testing applications with multiple identical objects, QuickTest assigns an ordinal identifier to each test object. This may lead to unreliable object identification. However, it may not (immediately) result in a failed step.
A visual relation identifier is a set of definitions that enable you to identify the object in the application according its neighboring objects in the application. You can select neighboring objects that will maintain the same relative location to your object, even if the user interface design changes. This enables you to help QuickTest identify similar objects much as a human tester would, and helps in creating more stable object repositories that can withstand predictable changes to the application’s user interface.
How Visual Relation Identifiers Work
Suppose that you are shown a photograph of a classroom, and are then asked to note identical twins sitting at different desks, and to be able to identify each twin successfully when shown different photographs of the same classroom at a later time.
You are told that one differentiating characteristic is that one twin always carries a blue school bag, and that the other twin always carries a red school bag. You are then also told that each twin has an assigned desk partners, which means that even if the twins sit at a different desk in other photographs, they always sit next to their assigned lab partners.
Therefore, the solution is to identify the twin with the blue school bag in this manner: <twin> is nearest to <twin’s desk partner>, and carries <blue school bag>.
QuickTest uses visual relation identifiers in a similar manner, by examining related objects in the application that you are testing. However, because QuickTest compares the related objects based on their relation to the test object to identify as a set of definitions, you would state that <twin’s desk partner> is nearest to <twin>, and not vice versa.
Watch the Visual Relation Identifiers movie to see a demonstration of how this functionality can be used in an end-to-end process.
You are told that one differentiating characteristic is that one twin always carries a blue school bag, and that the other twin always carries a red school bag. You are then also told that each twin has an assigned desk partners, which means that even if the twins sit at a different desk in other photographs, they always sit next to their assigned lab partners.
Therefore, the solution is to identify the twin with the blue school bag in this manner: <twin> is nearest to <twin’s desk partner>, and carries <blue school bag>.
QuickTest uses visual relation identifiers in a similar manner, by examining related objects in the application that you are testing. However, because QuickTest compares the related objects based on their relation to the test object to identify as a set of definitions, you would state that <twin’s desk partner> is nearest to <twin>, and not vice versa.
Watch the Visual Relation Identifiers movie to see a demonstration of how this functionality can be used in an end-to-end process.
NOTE : — > QuickTest uses visual relation identifiers only when one or more objects match the test object’s description properties during the identification process. If no objects in the application match the test object’s description properties, then the visual relation identifier you defined is ignored, and QuickTest continues to Smart Identification (if defined for that test object class).
No comments:
Post a Comment