Forum Discussion

techgirlbb's avatar
techgirlbb
Contributor
7 years ago

Slow performance while identifying the object properties

Qs1:

Even thought I have updated the latest version 12.42, I am experiencing the slow performance in identifying the objects for one of application I am working on.

I read the forum topic

https://community.smartbear.com/t5/TestComplete-General-Discussions/Is-anyone-else-experiencing-extreme-slowness-in-TestComplete/m-p/159556/highlight/true#M29462

where in the proposed resolution is:

Just create a back up of your Name Mapping Object and merge with it again. After deleting your data.  This solved it for me.

 

can you elaborate what is meant by backup of name mapping object? do I need to create a new project and identify that object and then merge it with main name mapping? 

 

Q2:

I have noticed that TC is selecting the extended find by default for most of the objects. As it was mentioned slow performance is due to extended find on the above article. In that case if I remove the extended find option, still TC able to identify the object? or do I need to add more properties to identify it. Never done it before. please share your expertise.

 

 

 

 

 

 

  • shankar_r's avatar
    shankar_r
    Community Hero
    7 years ago

    Some tips to your Q2:

    Extended Find can eat some performance but it is based the way you configure and the way your AUT behaves.

     

    If you have similar objects in your screen which you haven't given unique property to identify by using NameMapping then you will see the slowness in execution.

     

    To answer your Qs1;

    I guess the reason behind slowness of you execution after merge maybe you might have same objects in both NameMapping which may collapse your basic logics. YOu need to be very causes on merging name mapping.

     

     

     

  • Marsha_R's avatar
    Marsha_R
    Moderator
    7 years ago

    The solution in the link you found isn't clear at all. Have you actually done a merge?

  • sreedevtr's avatar
    sreedevtr
    Contributor
    7 years ago

    Enabling extended search by default can indeed affect the performance. Use extended search for a control only if we cannot identify a parent control associated with the control uniquely( May be the properties that can be used to identify the control gets changed dynamically at run time). In this case we will try to define the object hierarchy based on a parent control which can be identified uniquely. This is accomplished by enabling Extended Search for the control and by dragging the control just under the parent control that can be identified uniquely. In this case what happens is that TC will try to locate the control at all level below the parent control that can be identified uniquely. This can have an impact on performance. Also we will have problem if we have more than one control having the same set of property any where in the hierarchy below parent control.