Micro Focus QTP (UFT) Forums
QTP identifies the Wrong Object while running? - Printable Version

+- Micro Focus QTP (UFT) Forums (https://www.learnqtp.com/forums)
+-- Forum: Micro Focus UFT (earlier known as QTP) (https://www.learnqtp.com/forums/Forum-Micro-Focus-UFT-earlier-known-as-QTP)
+--- Forum: UFT / QTP Others (https://www.learnqtp.com/forums/Forum-UFT-QTP-Others)
+--- Thread: QTP identifies the Wrong Object while running? (/Thread-QTP-identifies-the-Wrong-Object-while-running)



QTP identifies the Wrong Object while running? - subramanianmsc2007 - 05-09-2012

Hi,

I have automated the 100 TCs using QTP 11, sometimes QTP does not identifies the correct object, it was clicked some other objects. But it happen sometime only, If the same TC executed again it is working fine. I have checked the object in object repository and highlighted, It was highlighted the correct object. I can't identify the problem. Could you please help me on this? Thanks in advance.




RE: QTP identifies the Wrong Object while running? - Ankesh - 05-09-2012

Please check the object again in OR. It might be using index property which inturn highlights some similar kind of object during runtime.

If Yes, remove the index from the object property list.

Regards,
Ankesh


RE: QTP identifies the Wrong Object while running? - Jyobtech - 05-10-2012

Hi Earlier I had faced same problem with SAP GUI application,
I overcome this situation like this , First log out the application then execute the test cases then it will work fine .
If you not log out the application properly sometimes QTP does not identifies the correct object and clicked some other objects.


RE: QTP identifies the Wrong Object while running? - mrinal_nandi - 05-11-2012

Even I have faced similar situation earlier while doing automation siebel application. For siebel application, we need to use special url to identify the siebel object( This url store some siebel object in to local System).
If we face issue with object identification, then we need to remove those object from browser and re run the test case again.
Please let us know the type of application you are using.