When a tested application is launched in the Debug mode, TestComplete traces the application run and reports information about debug strings, exceptions and other events that occur in the application’s process. See Tracing Events and Exceptions With Debug Services.
You can view and change Debug mode parameters in the TestedApps editor. The parameters are organized into two sections - Basic Parameters and Run-Mode Parameters.
Basic parameters include the following:
|Name||The unique name of the tested application in the Tested Applications collection. This name is used to refer to the application in tests, for example, in the Run TestedApp keyword test operation.|
|Run Mode||The mode in which TestComplete will launch the application:
|Count||This parameter is ignored.|
|Autorun application on recording||Select this option to have the application launched automatically when you start test recording.|
|Launch application from tests||Uncheck this option to prevent the application from being launched by the Run TestedApp keyword test operation and the
For example, you can define several instances of the tested application with different configurations and “disable” those not needed at the moment.
The following parameters are specific to the Debug run mode:
|Application||The name and path of the application executable file (.exe, .com, .bat or .cmd). You can enter the path manually or click the button and browse for the needed file.
The path can be fully-qualified or relative to the project folder. To switch between the fully-qualified and relative path representations, click the drop-down button and select the desired path in the drop-down list.
You can use environment variables, such as %PROGRAMFILES%, as well as project and project suite variables in the format $(VarName) in the file path. For more information, see Using Variables in Tested Application Paths.
If the application resides in a folder that is in the
|Command-line parameters||The command-line arguments that will be used to launch the application.|
|Working folder||The working folder for the application run. You can enter the folder path manually or click the button and browse for the needed folder.
The folder path can include environment variables, such as %PROGRAMFILES%, as well as project and project suite variables in the format $(VarName). For more information, see Using Variables in Tested Application Paths.
About Tested Applications
Tracing Events and Exceptions With Debug Services
Run Modes and Parameters
Using Variables in Tested Application Paths
Working With Tested Applications in Tests