Hi !
Some times ago, I noticed that using NameMapping with a lot of objects, is incredibly slow, even if the hierarchy is correct.
So now, I avoid it almost completely (less than 10 objects), and no more slow down since.
Hi,
Is "Extended Find" checked for any levels in that branch of your name mapping hierarchy (i.e. Aliases.browser.pageD365.sectionLanguage.panelRecentlyUsed)? My experience is that translates to extra slow mode. I avoid it at all costs. It requires more work getting all the levels of hierarchy mapped but it worth it IMO.
Name Mapping - Extended Search | TestComplete Documentation (smartbear.com)
As Marsha suggested, it could also be the results of the object state. However, I wouldn't expect a 22 second delay unless your auto-wait in the project properties is set really high. I think five to ten seconds it the default.
Lastly, are there a ton of child objects? If there are a dozen that should be quick. If there are a thousand that's a different story. We have a tree control in our app that has ~10000 children. It takes several minutes to click anything in that tree.
Best regards, John
While the actual DOM object only has about 20 children (not including the children's children, and their children, etc.), the Namemapping object has a lot of "siblings". Basically, there is my page object: page1, and page1 has over 300 children, the object w being one of them. If you think that's the place to start, I'm going to try to build more hierarchy into the Namemapping file and see if that improves performance.
