11-04-2009, 01:13 PM
Hi Saket,
I would like to share my point of view on your below comment.
"Incase the assistive properties are also not enough to uniquely identify an object QTP uses the ordinal identifiers ie -index, location and time of creation of the object. If all this fails QTP resorts to the smart identification mechanism."
As per your way: Mandatory&Assistive --> Ordinal Identifer --> Smart Identification.
In my perspective: Mandatory&Assistive --> Smart Identification --> Ordinal Identifier.
Since QuickTest records a value for ordinal identifier only as backup when it cannot create a unique description using all available mandatory and assistive properties.
Further, even if QuickTest records an ordinal identifier, it does not use it to identify the object during the run session, unless neither the recorded description(Mandatory/Assistive) nor the Smart Identification mechanism are able to single out the object in your application. If the other test object properties are sufficient to identify the object during a run session, the ordinal identifier is ignored.
@Ankur/Saket: Please correct me if I am wrong in the above context
I would like to share my point of view on your below comment.
"Incase the assistive properties are also not enough to uniquely identify an object QTP uses the ordinal identifiers ie -index, location and time of creation of the object. If all this fails QTP resorts to the smart identification mechanism."
As per your way: Mandatory&Assistive --> Ordinal Identifer --> Smart Identification.
In my perspective: Mandatory&Assistive --> Smart Identification --> Ordinal Identifier.
Since QuickTest records a value for ordinal identifier only as backup when it cannot create a unique description using all available mandatory and assistive properties.
Further, even if QuickTest records an ordinal identifier, it does not use it to identify the object during the run session, unless neither the recorded description(Mandatory/Assistive) nor the Smart Identification mechanism are able to single out the object in your application. If the other test object properties are sufficient to identify the object during a run session, the ordinal identifier is ignored.
@Ankur/Saket: Please correct me if I am wrong in the above context