Re: What is the best record strategy (real-time, e
Actually, I only use the record feature to gauge the sequence of forms, GUI component names, etc, that are needed during a script. Once I figure that out, I usually end up writing some sort of library routine(s) to perform common tasks and then write my test cases manually in code.
One suggestion for you: you say that your recorded scripts fail because they run too fast on play back. We have that problem with our AUT. The problem is that the scripts just keep on clicking and keyboarding even though the form or child object hasn't yet been displayed by the AUT (especially if it needs to populate information from a large data source). What we do is we use WaitProcess, WaitChild, and WaitWindow extensively. Look up these methods in the TestComplete help for more information on usage. By using these, you can make your scripts "smarter", making the same decisions that we humans instinctively make. We don't click on a button until we can see the button. What I needed to do for my AUT is make sure that the script routine makes the same decisions...don't act on a form/component until the form/component is available for action.