Forum Discussion
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.
Simply turning off extended find does not resolve performance issues... in fact, it could make things worse in your automation. Extended Find "compresses" the mapping tree by telling the NameMapping engine to search the entire tree of descendants for the object that matches the properties. So, if you want to turn off extended find, you need to more fully map your objects.
For example, say in the Object Browser, you see the following:
Sys.Browser('chrome').Page('http://mypage.com').Panel(0).Panel(1).Panel(0).TextNode(0)
And you tell TestComplete to map the TextNode. If TC is configured to use extended find whenever possible, you may see in your NameMapping the following
NameMapping.Sys.browser.pageMyPage.TextNode
The TextNode will have the Extended Find flag checked. If you want to uncheck it, you will need to manually add mapping for the three panels that were skipped. That's what that article means when it talks about mapping additional parent objects.
Related Content
- 3 years agothaidy