Hi !
Some times ago, I noticed that using NameMapping with a lot of objects, is incredibly slow, even if the hierarchy is correct.
So now, I avoid it almost completely (less than 10 objects), and no more slow down since.
It looks like you have identified the issue - now ask yourself, does the child object have a click method? Is the child object visible? and is it enabled (as Marsha_R has mentioned)? For TestComplete to perform the appropriate action?
All standard objects will have the Name property. Hence, this will work fine.
The delay is most likely relating to your project settings for playback,
Error messages in the log should give you an indication as to what the possible cause is.
Thank you for your advice! Because the test does run, evidently the object is clickable, and the objects is visible and enabled for a user the whole time. I will definitely investigate further about those properties.
The strange things is that when the Auto-wait timeout is running, there is always an indication from that status box in the top right, where it will say "waiting until object x is visible" or "searching for object x". In this case, there just the normal message even when nothing is happening during the delay:
I'm going to try to shrink down my Namemapping bloat, and I will get back to all of you about how that works.
Thank you,
Hi !
Some times ago, I noticed that using NameMapping with a lot of objects, is incredibly slow, even if the hierarchy is correct.
So now, I avoid it almost completely (less than 10 objects), and no more slow down since.
While cleaning out my existing Namemapping file was not an option, a new Project with an empty Namemapping file proved your idea correct! It is like lightning now, and I will try to keep this Project that way, and exclusively use it for tests like this.
Thank you very much!
I thought of one more setting that has been responsible for slowness for us in some instances. If the object you are trying to click happens to exist but is hidden when you attempt to click it having the below setting can cause a big delay. "Hiden", or not hidden, is reflected by the "VisibleOnScreen" property. The scenario for slowness is the object exists but VisibleOnScreen is False when you try to perform some action on it.
I doubt this applies to your scenario though.
