|Adding web browsers and web applications to the Tested Applications collection is obsolete. Starting from version 14.0, it is no longer possible to add them to the collection directly.
To launch a web browser from tests, use the Run Browser keyword test operation or the
The Tested Applications collection can include Web browsers and web pages. Parameters of Web applications 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.|
|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.
|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 Web applications in the Tested Applications collection:
|Page URL||The URL of the web page to open in the browser. If the web page is stored on the local computer, you can click the ellipsis button and browse for the web page file.|
|Web Browser||The browser to launch. You can choose the needed browser from the drop-down list or press the button and browse for the browser executable file.|
|Command-line arguments||Command-line arguments to be passed to the web browser.|