Hi everyone, I am currently on TestComplete 12.10 Build 602 and experiencing performance issues when trying to edit On-Screen actions in Keyword Tests. I am building an automation suite for Microsoft Dynamics CRM 2016 and have been experiencing performance problems in general, so that might be why I am having this issue. It really is making TestComplete unusuable because I need to edit many of the On-Screen actions that get recorded and it takes 5+ minutes to load the On-Screen edit box. Has anyone else had this problem and do you know what I need to do to solve it? Thanks! vondie

SarahEdwards wrote: In my experience, "As soon as I remove the extended find, any steps using that object are broken." I asked SmartBear technical support, "Is there a better way than remapping every object?" Yuriy Peshekhonov from SmartBear Customer Care said: Unfortunately, there is no other way. TestComplete uses a different logic when recording a test using the "Extended Find" feature. It's not enough to uncheck the option for an object in the Name Mapping. You need to delete the existing Name Mapping scheme and map the object without using "Extended Find". TestComplete doesn't store the information on how to find the object with/without "Extended Find" at the same time, so it's not possible to quickly switch between using "Extended Find" and not using it. Correct... unchecking the option under NameMapping for an already mapped object won't "work" then because, as YuriPeshekhonov points out, you have changed, effectively, the method by which that specific object is found... But the option under Tools -> Options -> Engines -> NameMapping, if you uncheck it, won't impact anything you already mapped.

Slow to Load On-Screen Actions for Edit

10 Replies

SarahEdwards
Contributor
9 years ago
Copy Link
I was having delays like this when my name mapping was using "extended find" on every object. That is a default setting.

I had to scrap my project and remap everything.

I really hope this isn't the case for you.

vondie wrote:
Hi everyone,

I am currently on TestComplete 12.10 Build 602 and experiencing performance issues when trying to edit On-Screen actions in Keyword Tests. I am building an automation suite for Microsoft Dynamics CRM 2016 and have been experiencing performance problems in general, so that might be why I am having this issue. It really is making TestComplete unusuable because I need to edit many of the On-Screen actions that get recorded and it takes 5+ minutes to load the On-Screen edit box. Has anyone else had this problem and do you know what I need to do to solve it?

Thanks!
vondie
- tristaanogre
  Esteemed Contributor
  9 years ago
  Copy Link
  Correct, you don't need to use Extended Find on every object. It is a useful tool for those parts of web applications that are extremely dynamic (had a web app that I was testing where the hierarchal organization of elements on the page changed, literally, on an hourly basis... extended find saved me a LOT of time there). But it comes with overhead in that every object that has that flag checked needs to be "found" within the tree so there is some processing time to search for it.
- vondie
  Contributor
  9 years ago
  Copy Link
  Can you enlighten me on how to disable it and if it's always necessary to start over with the project if Extended Find had been enabled previously? I already saw in the Options menu that the checkbox for "Use extended find when possible" was checked (as stated that it was the default). I'm curious what will happen with my existing project if I uncheck that now after having built 8 or so tests with the Extended Find enabled.
  
  Any help is appreciated, thank you for the response!
  - tristaanogre
    Esteemed Contributor
    9 years ago
    Copy Link
    Unchecking the option won't change anything you already have mapped. All that does is configure that, when TestComplete is automatically mapping your objects, that it will check that flag if it makes sense... and many times it does make sense.
    
    Again, Extended Find is a GOOD thing for the most part... but it can give a performance hit if it is used a lot. There's a "sweet spot" somewhere in every project... I can't necessarily tell you what that is for yours but I think you'll find that some places it makes sense and some places you can do without.
    
    See the last section of this article...
    
    https://support.smartbear.com/testcomplete/docs/reference/options/engines/name-mapping.html