QTP support tip: What to do if QTP/UFT suddenly stop recognizing a control.
If there is a scenario where you have a working script running and suddenly it shows an error saying that a control is not found there are some action you can perform to repair it.
Some times this is caused because developer change name, properties or code of the control in the Application Under Test (AUT); or a change was performed in the recognition properties of the control directly from the object repository.
In order to fix this you can do the following:
1) Open the AUT and search for the control in question.
-Open the object repository and delete the problematic control.
-Use the Add Object to Local button in order to Add the control again.
2) Click on UFT Menu Run>Maintenance Run Mode. On QTP Menu Automation>Maintenance Run Mode.
Start running the script and perform the modifications:
When it cannot identify an object, the Maintenance Run Wizard opens (instead of the standard error message).
On the first screen QTP/UFT suggests 2 options:
1. Point to the Object
2. Add a Comment
Point to the Object – This will allow QTP/UFT to determine how to change the script to use that object.
Add a Comment – This will not fix the script; just add a comment so you can address it later.
If you find that this or any post resolves your issue, mark it as an accepted solution.
Note: The Opinions expressed in my post are mine alone, and do not reflect the opinions of my employer. No warranties express or implied for any answered posted.