Application Details Dialog Box
This dialog box enables you to add details for an application or to edit details for the application that you selected in the Windows Applications tab of the Record and Run Settings dialog box.
To access |
In the Windows Applications Tab (Record and Run Settings Dialog Box), click the Add button or Edit button . |
Important information |
|
See also |
User interface elements are described below:
UI Elements |
Description |
---|---|
Application |
The executable file on which to record. You can enter the executable file as a relative path. During the run session, OpenText Functional Testing searches for the file in the folder for the current test, and then in the folders listed in the Folders pane of the Options dialog box (Tools > Options > GUI Testing tab > Folders node).
You can specify a document or other file associated in the file system with an application, for example, c:\tmp\a.txt. In this case, OpenText Functional Testing automatically opens the specified file in the associated application (Notepad in this example). If you use this option, OpenText Functional Testing ignores any defined program arguments. |
Working folder |
(Optional) The current working folder for the application. The current working folder is used by the application to search for related files. If a working folder is not specified, the executable folder is used as the working folder. This parameter is used only when Launch application is selected. If Launch application is not selected, its value has no effect. |
Program arguments |
(Optional) Instructs OpenText Functional Testing to open the application using the specified command line arguments. This parameter is used only when Launch application is selected. If Launch application is not selected, its value has no effect. |
Launch application |
Instructs OpenText Functional Testing whether to launch the selected application when the record and run session begins. |
Include descendant processes |
Instructs OpenText Functional Testing whether to record and run on processes created by the specified application during the record and run session. For example, a process that is used only as a launcher may create another process that actually provides the application functionality. This descendant process must therefore be included when recording or running tests on this application. Otherwise, the functionality is not be recorded, or the run session fails. By default, this option is selected. |