The Tested Applications collection can include applications with the RunAs run mode, that is, configured to run under a specific user account. See Testing Applications Running Under Another User Account.
You can view and change application parameters, such as the application path and the user account, 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||The number of application instances that will be simultaneously launched during the test recording or run.|
|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 tested applications with the RunAs 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
|User name||The user account to launch the application under. This account must have a non-empty password.|
|Domain||The name of the domain or computer to which the account belongs.|
|Password||The password of the specified user account. The password characters are masked by dots for security purposes. The password is stored securely in one of the project files and encrypted using RC4 algorithm.|
|Command-line parameters||The command-line arguments to be passed to 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.
Using the RunAs run mode requires that the Secondary Logon service be running in Windows.
In order for TestComplete to be able to test an application launched under another user account, TestComplete must be running with administrator privileges. See also Using TestComplete With Administrator Privileges.
In order for TestComplete to have access to native properties and methods of application objects, the account under which TestComplete is running must have Default Access Permissions on the current computer. For more information, see Settings for Testing Open Applications in RunAs Mode.
Testing Applications Running Under Another User Account
About Tested Applications
About TestedApps Editor
Run Modes and Parameters
Using Variables in Tested Application Paths
Working With Tested Applications in Tests