Relevant for: GUI tests and components
Each object in your test or component is identified relative to its parent objects.
If you received a Cannot identify object error despite the fact that you can see the object in the application, and the object appears to have the same object property values in the object repository and in the Object Spy, the problem may be with the description of one of the parent objects specified in the step, or the object may simply have a different object hierarchy than when UFT One learned the object.
To identify which object in the object's hierarchy is causing the problem, try one of the following:
Re-record a step on the object in your application and compare the parent objects of the newly learned object with the parent objects of the problematic object. Then compare the parent object hierarchies for both objects. If the parent object hierarchies are the same, compare the parent object descriptions in the object repository.
Click here for step-by-step instructions on how to perform this comparison.
Insert an Exist statement for each parent object in the object hierarchy and run this part of the test or component.
Click here for step-by-step instructions on how to create the Exist statements.
Tip: You can also use the Highlight in Application option in the Object Repository window to locate a selected object in your application.
After you find the problem with the object's parent hierarchy, try one of the following solutions:
- Fix the object description of the problematic parent object using the suggestions for Solve object description problems.
- Find all instances of the old hierarchy in the Editor and replace it with the correct object hierarchy as described in the example in Re-record an object to identify parent object description problems.