Forum Discussion

Contributor

5 years ago

Taking time to object identification in testcomplete 14.4 through chrome browser

Sys.Process(g_strBrowserType).Page("*") we are using but it checking all process for chrome and identifying object taking time.same script will run in ie 2 minutes but in chrome more than 15 minutes....

tristaanogre
5 years ago
And Page('*') means that you're searching, basically, all pages.... which, if you have a bunch of tabs open, can take a bit.

And Find and XPath logic do a search, scanning the object tree... which can take some time. That's why TestComplete has NameMapping. The engine for NameMapping is much more processor efficient that those other methods and can speed up your work. So, yes... why not NameMapping?

Wamboo

Community Hero

5 years ago

Hi,

Did You try t use NameMapping instead of directly access Sys memory vaules?

BenoitB
Community Hero
5 years ago
In addition to Wamboo question, which kind of check do you make ? TC xpath or TC specific ? Xpath is very slow and especially on Chrome.
- tristaanogre
  Esteemed Contributor
  5 years ago
  And Page('*') means that you're searching, basically, all pages.... which, if you have a bunch of tabs open, can take a bit.
  
  And Find and XPath logic do a search, scanning the object tree... which can take some time. That's why TestComplete has NameMapping. The engine for NameMapping is much more processor efficient that those other methods and can speed up your work. So, yes... why not NameMapping?
  - sonya_m
    SmartBear Alumni (Retired)
    5 years ago
    Thanks everyone for helping here.
    
    Babulu Did you resolve the issue? Please update us on your progress, and we will see how we can help. Thank you.
- Babulu
  Contributor
  5 years ago
  same chrome browser we are using another appliation. That application is very fast to identify the objects and execution but related to flex and java related application is very very slow to idnetify the obects.