Hi Bhavin,
If QTP is not able to identify the Object uniquely using Mandatory + Assistive Property OR Smart identification mechanism (if configured), Ordinal identifier comes to our rescue.
In such a scenario QTP uses recorded description + Ordinal identifier to identify the object, if combined recorded description and ordinal identifier are not sufficient to identify the Object QTP stops and throws the Run Time Error
.
So there are 3 types of Ordinal Identifier:
1. Index
2. Location and
3. Creation Time (Specific to browser)
Index is a Numeric value based on the order in which the object appears within the source code. Index is 0 based.
If index is selected as an ordinal identifier then the QTP will generate the sequence of the number starting from 0,1,2.... and so on based on the sequence of corresponding Objects in the program.
For Example:
If you use index: =2 to describe a link test object, QTP searches for the 3rd Link object on the page.
If you use index: =2 to describe a WebElement object, QTP searches for the 3rd object on the page irrespective of type.
Please let me know if require more explanation.
If QTP is not able to identify the Object uniquely using Mandatory + Assistive Property OR Smart identification mechanism (if configured), Ordinal identifier comes to our rescue.
In such a scenario QTP uses recorded description + Ordinal identifier to identify the object, if combined recorded description and ordinal identifier are not sufficient to identify the Object QTP stops and throws the Run Time Error
.So there are 3 types of Ordinal Identifier:
1. Index
2. Location and
3. Creation Time (Specific to browser)
Index is a Numeric value based on the order in which the object appears within the source code. Index is 0 based.
If index is selected as an ordinal identifier then the QTP will generate the sequence of the number starting from 0,1,2.... and so on based on the sequence of corresponding Objects in the program.
For Example:
If you use index: =2 to describe a link test object, QTP searches for the 3rd Link object on the page.
If you use index: =2 to describe a WebElement object, QTP searches for the 3rd object on the page irrespective of type.
Please let me know if require more explanation.