The Tested Applications collection can include AIR applications. Parameters of AIR applications under test in the TestedApps editor 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.|
|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.
|Use special runtime object||
This option controls the scripting interface to the tested application.
If it is enabled, you can get and set the application parameters directly via the
If it is disabled (not recommended except for legacy tests),
The following parameters are specific to AIR applications in the Tested Applications collection:
|Run application under AIR debugger||
Use this option if you are testing an unpackaged AIR application specified by the application descriptor file.
|Specify AIR application executable||Use this option if you are testing an installed AIR application. In the edit box, specify the path to the application’s executable file (.exe).|
|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 file and folder paths manually or click the button and browse for the needed files and folders.