TestComplete Desktop v12.10 is very verys low to record and playback.

Question

I am learning to record macros using the Orders application (C# version). Even the most basic operations, such as going to the file menu to open a file through the Orders application, is taking 30 seconds or more just to get the file dialog box to appear. I have tried using TestComplete on one of our very large applications written in C++ and it just appears to hang (I have had to wait minutes to perform simple operations).

I am hoping that there is something I can do to tune the product and make it run faster. As it is now, it is much too slow to be of practical use for us.

I have turned of image capturing during the recording process and that does not seem to help.

Any ideas?

Thanks.

tristaanogre · Answer

One of the things that is being done while recording your test is that objects need to be identified so that they can be added to the NameMapping when the recording is complete. Depending upon the complexity of the application, the types of objects and controls being used, etc., this NameMapping can take a bit.

You could try turning off automatic NameMapping (Tools | Engines | NameMapping) but that would mean you'd have to come back and map the items manually after the fact. You could at least try it as a diagnostic to see if this is the problem.

tristaanogre · Answer

OK, on playback (and possibly recording), again it has to do with object recognition. &nbsp;In your NameMapping file, are you utilizing the "Extended Find" option on some of your objects? &nbsp;If so, one thing that is happening is that, when TestComplete goes to identify your object that you want to interact with, it needs to "find" it and the Extended Find does a breadth-first search of the component tree to find your object. &nbsp;The best way to get around this is to map additional "parent" objects in your tree to reduce the amount of searching needed.
&nbsp;
Secondly, you say that the majority of the problem happens on opening a new form. TestComplete needs to recognize that the form exists and child objects on the form exist before it can proceed. &nbsp;So, if you click on a button and it opens a new form and you want to do something with that new form, TestComplete needs to first find that form before it can interact with it. &nbsp;There is, in Tools | Current Project Properties | Playback an option called Auto-Wait Timeout. &nbsp;Most of the time, this defaults to 10 seconds. &nbsp;If TC needs to recognize your components before interacting, this wait may come into play. &nbsp;If it's something other than 10 seconds, that's probably where your long delay is.
&nbsp;
Finally, under tools | Options | Engines | NameMapping there is an option for "search for visible objects first". &nbsp;Turn that off and see if that increases your performance.
&nbsp;
Beyond that... since there are not too many other people reporting the same performance problem, this could be something localized to your environment. &nbsp;Try temporarily disabling virus scanners and such in your test environment, double check your memory and processor levels, etc. &nbsp;Also, it might help us if you can post pictures of code segments of where the problem is occurring and, perhaps, screenshots of the full Advanced properties listing of the objects in question in your TestComplete object browser.

baxatob · Answer

First of all:&nbsp;https://support.smartbear.com/testcomplete/docs/working-with/best-practices/performance-tips.html

clay · Answer

Robert,&nbsp;Thanks for the reply.&nbsp; Your suggestion makes a lot of sense to me (delays occur immediately after a new window opens - then there is an "explosion" of activity until the next window opens, then repeat...).&nbsp; However, I turned off the name mapping&nbsp;and I can see no change in performance.&nbsp; The tests run to completion, so some sort of mapping is apparently still taking place even though I turned off the mapping per your suggestion.&nbsp;I have not taken an in-depth look at the previous reply, but will be doing so in a few minutes.&nbsp;Thanks again.&nbsp;Clay

clay · Answer

Generally good information.&nbsp; Thanks for the post.&nbsp;&nbsp;I have been through a major portion of the material, but I haven't found anything fixes to my problem yet.&nbsp; I see minor improvements, but the main problem - 30+ second delays - still persists.

Forum Discussion

TestComplete Desktop v12.10 is very verys low to record and playback.

9 Replies

Related Content

TestComplete Playback Failing

TestComplete Desktop testing

TestComplete Playback test

TestComplete kill process of target desktop app

TestComplete Desktop Script Execution

Recent Discussions

TestComplete14.72 is not recognizing WinUI-3 objects

Floating window bleep overlapping window takes longer time (~10 min) to click the button on it.

Test case randomly fails with "parent object was not found"

Does TC have a .within() method similar to Cypress.io?

SessionCreator /Timeout option not firing EventControl_OnTimeout