Forum Discussion
Let's see an example of the code that runs slow and the name mapping that relates to it.
- vondie7 years agoContributor
Here are some screenshots of the Keyword Test in question and the name mapping/object browser for the test. I am having issues starting on the textboxFirstnameI field and it continues for the remainder of the test.
- Marsha_R7 years agoChampion Level 3
I see Extended Find selected for many of your objects. That can certainly add to the search time. This link can help you reduce some of that:
- vondie7 years agoContributor
Thanks for the reply! I tried different variations with having all of the textbox objects Extended Find unchecked and leaving everything else checked, leaving textbox objects Extended Find checked and the parent levels unchecked and it seems to get worse if I turn Extended Find off for any of the objects. I have also tried this from the link that you sent without seeing a performance improvement:
Searching for objects in large applications may take a long time. If you get warnings in the test log that a search takes too much time, try doing the following:
Add more objects to the object’s parent hierarchy in the Mapped Objects tree to narrow the search. For instructions, see About the 'Search for a Mapped Object Took Too Much Time' Warning.
- sreedevtr7 years agoContributor
I think we should use Extended find only if one or more of the parent components in the object hierarchy cannot be identified uniquely(For EG : Property values get changed dynamically). In this case we will identify a parent object that can be identified uniquely and will enable Extended Find for the child object we are trying to map and child will be dragged and placed under the parent control that can be identified uniquely. But this have the following short falls : It will search all the child controls under the parent control that can be uniquely identified for a match which will be indeed time consuming. Also this approach will have an issue if we have more than one control matching the property value selected for the child control even at a different object hierarchy