Sometimes, at the point of an application launch, we need to know the details like which modules are being loaded by the application in view. To this end, TestComplete has an option for launching a debugger mode.
In order to run a tested application in Debug we need to perform the following steps:
In the result, as shown in the following screenshot, the log will have the information about all the files that are being uploaded by the application at the point of launch:
When we start the application in the Debug mode, TestComplete takes over as debugger for the application and keeps track of all the modules that have been uploaded by the application, all the emergent exceptions, and so on.
It is also possible to view detailed information for each individual message. To do so, one should click on the message in the log and switch to the Additional Info tab (under the log messages).
Meanwhile, a vast amount of information is entered to the log, thereby making it cluttered, this is why it is recommended that the Debug option should be used only in case of need (for example, if the application triggers fallback closing at the point of being launched, due to some unknown reasons), in other cases a simple mode is used.
Besides, in the Debug mode, the application works slower than in the simple ordinary mode.