General Recording Specifics
When recording user actions, TestComplete takes into account various factors and events that occur in the system and in the application under test. These factors and events affect the test commands that TestComplete records:
-
During recording, TestComplete recognizes windows and controls with which you are working, and records user actions as calls to methods and properties of these objects. If it is impossible to do that, TestComplete resorts to recording mouse clicks with coordinates and keyboard events. Low-level recording like mouse movements or pressing and releasing mouse buttons is also possible, but in many cases it is not so convenient as object-level recording.
-
Depending on the tested application and on its controls, keyboard input can be recorded with the
SetTextorKeysmethod call. -
Some third-party software can prevent recording keyboard events.
-
And so on.
We recommend that you read the Recording Specifics topic that mentions the points you should pay your attention to and describes possible issues and workarounds. The sections below describe the specifics of recording tests for web applications.
Ignoring Dynamic Parameters in URLs
By default, TestComplete records the complete URLs of web pages, including query strings. However, query parameters can change, which can cause errors when accessing the pages during subsequent test runs. To ignore query string changes, use the Ignore dynamic URL parameters project option. For more information, see Ignoring Query String Parameters.
Silverlight Applications
When TestComplete records user actions invoking a common dialog box like Save File or Open File in a Silverlight application, the “Dialogs must be user-initiated” security error may occur. This happens due to some security restrictions in Silverlight.
To get more details on this issue and to learn how you can workaround it when recording tests for a Silverlight application, see –
Recording User Actions Over Silverlight Applications - Specifics