Identify test object description problems

Relevant for: GUI tests and components

If you receive a Cannot identify object error message even though you can see the object in your application, then there is a discrepancy between the test object description saved in the object repository and the object description in the application.

If you believe that this problem is due to an intentional change in your application

and you expect that there may be other such discrepancies due to the changes made in your application, we recommend stopping the current run and use the Maintenance Run Mode option.

When you run a test or component in Maintenance Run Mode, UFT One runs your test, and then guides you through the process of updating your steps and object repository each time it encounters a step it cannot perform due to an object repository discrepancy.

If you believe that the object description problem is an isolated occurrence

you can fix it manually. The first step in solving object description problems is finding the discrepancy.

The easiest way to do this is to compare the property values of the test object with the property values of the corresponding object in your application (using the Object Repository and the Object Spy).

Click here for step-by-step instructions on how to perform this comparison.

After performing the comparison, did you find one or more conflicting object property values?