Forum Discussion

Adagio's avatar
Adagio
Frequent Contributor
7 years ago

Object recognition is too slow

Hi, I've an app which I'm trying to automate.   some of these controls are so deep inside the DOM, that the object mapping took in 10 minutes for mapping 1 object. Problem was even worse whil...
  • tristaanogre's avatar
    tristaanogre
    7 years ago

    There's another option in Tools | Options | Engines | NameMapping about "find visible objects first" or something like that.  Turn that off.  Having that on has TestComplete filter out objects with the "Visible" property set to "False" and, if it can't find the object as visible, it then goes back and RE-searches the object.  With that option turned off, the search is only done once.

Adagio's avatar
Adagio
Frequent Contributor

Thanks Robert! I tried the suggested approach, but that didn't solve the problem.

It's still taking a lots of time to get the mapping path of the object( for mapping). I deleted my old mapping and wanted to do it again, but no success. When I was trying to map it again, it took around 15 minutes to get me the mapping path, and asked me to map 28 objects before mapping this required object. 

 

Even for xPath, I wrote it in a way that It didn't have to go thru evey single node in the tree. I used the Ids and that could have been faster, but that didn't help either. 

Please let me know what you think.

 

Thank you

Abhi

tristaanogre's avatar
tristaanogre
Esteemed Contributor
7 years ago

There's another option in Tools | Options | Engines | NameMapping about "find visible objects first" or something like that.  Turn that off.  Having that on has TestComplete filter out objects with the "Visible" property set to "False" and, if it can't find the object as visible, it then goes back and RE-searches the object.  With that option turned off, the search is only done once.

  • Adagio's avatar
    Adagio
    Frequent Contributor
    7 years ago

    Yes Robert, I tried that too. But that didn't change much while mapping the object. Here's what I see....

    I'm trying to map an object, and this time it took 20 minutes to give me suggestions on how many objects  I should be mapping in order to map the object. This one asks suggests to map 28 objects. 

     

     

     

    Thank you

    Abhi

    • tristaanogre's avatar
      tristaanogre
      Esteemed Contributor
      7 years ago

      Actually, that's not unexpected.  If there are that many layers of objects between the application process and the target object, yes, you WILL get a lot of "You need to map this first".  That is the effect of turning off the Extended Find option.  The trade off is that you might have to map more objects initially, but your execution time will be sped up.  Also, once you map a parent object, it never needs to be mapped again so you will see a declining curve of effort the more objects you map.  And finally, mapping new objects won't have the overhead of the Extended Find "search" algorithm to find the object so you will see a performance improvement on that front as well.

       

      • tristaanogre's avatar
        tristaanogre
        Esteemed Contributor
        7 years ago

        Let me amend that... 20 minutes to come up with the suggestions... that's a bit of time, yes.  My question then would be what are the specifications of the machine that you're doing the work on.