Generally good information. Thanks for the post.
I have been through a major portion of the material, but I haven't found anything fixes to my problem yet. I see minor improvements, but the main problem - 30+ second delays - still persists.
Hang on... something in one of your previous posts doesn't add up.
You say that the tests run to completion but there are still delays.
So... question: The delays you are complaining about... are they happening on recording or on playback? Depending upon that answer, there may be a whole host of other things to check.
The delays are happening in both places. However, the concern that motivated my posts is on the playback. I do more editing than actual recording.
OK, on playback (and possibly recording), again it has to do with object recognition. In your NameMapping file, are you utilizing the "Extended Find" option on some of your objects? 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. The best way to get around this is to map additional "parent" objects in your tree to reduce the amount of searching needed.
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. 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. There is, in Tools | Current Project Properties | Playback an option called Auto-Wait Timeout. Most of the time, this defaults to 10 seconds. If TC needs to recognize your components before interacting, this wait may come into play. If it's something other than 10 seconds, that's probably where your long delay is.
Finally, under tools | Options | Engines | NameMapping there is an option for "search for visible objects first". Turn that off and see if that increases your performance.
Beyond that... since there are not too many other people reporting the same performance problem, this could be something localized to your environment. Try temporarily disabling virus scanners and such in your test environment, double check your memory and processor levels, etc.
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.
