Forum Discussion

vondie's avatar
vondie
Contributor
8 years ago
Solved

Slow to Load On-Screen Actions for Edit

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 Micr...
  • tristaanogre's avatar
    tristaanogre
    8 years ago
    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. 

SarahEdwards's avatar
SarahEdwards
Contributor

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. 

tristaanogre's avatar
tristaanogre
Esteemed Contributor
8 years ago
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. 

  • SarahEdwards's avatar
    SarahEdwards
    Contributor
    8 years ago
    tristaanogre wrote:
    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. 

    Sure, but you'll still have performance issues any time you try to edit the extended-find-enabled name mapped objects. If those are in a test that you'll edit often, I'd imagine that would be less than ideal.

    • tristaanogre's avatar
      tristaanogre
      Esteemed Contributor
      8 years ago

      No argument there, SarahEdwards... but as mentioned, it is useful for web page testing... all those panels and tables and cells and such are, effectively, useless from an automation perspective... and, as mentioned, they tend to change frequently depending upon the architectural decisions made by the development staff.  So, using Extended Find judiciously is a good thing... certainly don't use it for EVERY object, but make use of it were it makes sense.  Yes, there will be performance hits on it, but honestly, I'll take a little performance hit if it means that I don't have to remap a component just because some developer decided to wrap it in yet another <DIV> element

      • vondie's avatar
        vondie
        Contributor
        8 years ago

        Thank you for the responses. Everything you both said provided clarity into the issue. I did uncheck the box in Options/Engines/Name Mapping and haven't seen any negative consequences so far after remapping the objects that had performance issues. I would say this is solved for now. I appreciate all of your replies!