Working With the TestedApps Editor

Adding new tested applications

Editing tested application parameters

Renaming tested applications

Specifying the application run mode (for desktop Windows applications only)

Specifying the application command line and working folder (for desktop Windows applications only)

Running applications under other user accounts (for desktop Windows applications only)

Profiling applications with AQtime (for desktop Windows applications only)

Launching a tested application

Launching all tested applications

Deleting applications from the list

Saving the changes

1. Right-click anywhere within the TestedApps editor and choose Add Application from the context menu.

2. In the resulting Add Tested Application wizard, choose the type of your tested application and specify its launch parameters.

For detailed information on adding items to the tested applications list, see:

1. Select the desired application in the list.

2. In the Basic Parameters section of the editor, modify basic parameters of the application.

3. In the Run-Mode Parameters section of the editor, modify parameters of the application applied to the selected application run mode.

4. Save the changes.

1. Select the desired application in the list.

2. In the Name edit box of the Basic Parameters section of the editor, type the new application’s name.

3. Save the changes.

TestComplete can launch Windows-based applications in several run modes: Simple, RunAs, Debug, and Profile:

1. Select the desired application in the list.

2. In the Basic Parameters section of the editor, select the needed run mode from the Run-Mode list.

3. In the Run-Mode Parameters section of the editor, specify parameters for the selected run mode.

4. Save the changes.

For more information about tested application types and run modes, see Run Modes and Parameters. For a description of tested application parameters, see Run Modes and Parameters.

1. Select the desired application in the list.

2. Make sure that its run mode is set to Simple, RunAs, or Debug.

3. In the Run-Mode Parameters section of the editor, specify the desired command line or working folder settings in the appropriate edit boxes.

4. Save the changes.

The command line arguments are displayed in the footer area of the editor.

1. Select the desired application in the tested applications list.

2. In the Basic Parameters section of the editor, select RunAs from the Run-Mode list.

3. In the Run-Mode Parameters section of the editor, specify the user name, domain, password and working folder settings for the run.

4. Save the changes.

5. Make sure the Launch application from tests check box in the Basic Parameters section of the editor is selected.

Now, when you launch an application from TestComplete, the application will be launched under the specified user account. See Testing Applications Running Under Another User Account for more information on this.

You can run a tested application in Profile mode to trace its performance during the test run, by using AQtime, a profiling tool by SmartBear.

1. Select the desired application in the tested applications list.

2. In the Basic Parameters section of the editor, select Profile from the Run-Mode list.

3. In the Run-Mode Parameters section of the editor, specify parameters for the run, for example, the profiler you want to use, the name of the AQtime project and so on. For detailed information on parameters you can configure, see Profile Mode Parameters.

4. Save the changes.

Now, when you launch an application from TestComplete (from the TestedApps editor, from script code or from your keyword test), TestComplete will run AQtime and launch the application from it. For more information, see Integration With AQtime.

Not applicable to BitBar applications. To learn how to upload mobile applications to the BitBar device cloud and start a testing session for them, see Connecting to Mobile Devices and Opening Testing Sessions.

1. Right-click the desired application in the tested applications list.

2. Select Run Selected from the context menu.

The application will be launched in the mode specified by its Run-Mode parameter. TestComplete will launch as many instances of the tested application as specified by its Count parameter (the Count parameter is ignored if an application is run in the Debug or Profile run mode or if the application is launched on a mobile device).

For information on how to launch the tested application from scripts, see Working With Tested Applications in Tests.

To launch a tested application from a keyword test, use the Run TestedApp operation.

Select Run All from the TestedApps editor context menu.

The tested applications will be launched in the mode specified by their Run-Mode parameter. If the run mode is set to Simple or RunAs, TestComplete will launch as many instances of each tested application as specified by its Count parameter. If the run mode is Debug, TestComplete ignores the Count value and always launches one new application instance. If the run mode is Profile, TestComplete also ignores the Count value and launches the application under AQtime.

To learn how to launch tested applications from scripts, see Working With Tested Applications in Tests.

If you want to launch all tested applications from your keyword test, simply add the Run TestedApp keyword operation to the keyword test and select All Applications from the list of tested applications in the operation’s properties.

1. Select the desired application in the tested applications list.

2. Right-click the application and select Delete from the context menu or press Del.

To save changes made to the tested applications list, select File > Save from the TestComplete main menu.

To discard any changes, close the editor and click No when TestComplete asks if you want to save the changes.