Forum Discussion

Babulu's avatar
Babulu
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. Chrome Version is 80

  • tristaanogre's avatar
    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's avatar
    Wamboo
    Community Hero
    5 years ago

    Hi,

     

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

    • BenoitB's avatar
      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's avatar
        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?