Forum Discussion
Basically, that object recognition hint means that your code is attempting to access an on screen object that, due to any number of factors, cannot be found. Something is incorrect in how you are attempting to identify the object.
So... you need to go to your Descriptive Programming definition for that object and determine if you are properly identifying the object.
Additionally... if you let the automation continue through that notice, it will write to the test log an object recognition hint as a warning. Please post here the information that shows in the "additional info" tab for that log record.
One final note: Descriptive Programming is methodology for UFT/QTP... you're not using those tools any more. It's better for you to learn the recommended methodologies for TestComplete. Please review documentation for NameMapping as well as the FindChild, and FindAllChildren methods of TestComplete for recognizing and accessing UI objects in the application.
by providing the PropArray and ValueArray
- tristaanogre7 years agoEsteemed Contributor
Then most likely there's something wrong with your property and value arrays. You are attempting to find an object and then trying to access it... and the find failed. Examine your arrays and make sure they are correct.
- vinod_ryaka7 years agoOccasional ContributorYes object is not displayed I can see but I need to avoid the wait time for find it should come out not found object instead it's waiting too long say preparing for the object recognition hint... I just want to avoid the wait time
- tristaanogre7 years agoEsteemed Contributor
If the object is not found, then you need to have your code check for that.... the "Preparing for an Object recognition hint" is coming up because you're trying to access a non-existant object... So... avoid accessing the non-existant object. The problem is simply that.
Related Content
Recent Discussions
- 7 hours ago
- 7 days ago
- 10 days ago