1. Do one of the following:

   • Ensure that a GUI test, action, or component is in focus in the document pane.

   • Ensure that a GUI test, action, or component is in focus in the document pane.

2. Select Tools > Options > GUI Testing tab > Stingray node.

• If the Stingray Add-in is configured correctly, you may not need to make any modifications using this pane. However, if you did not run the Stingray Support Configuration Wizard after installing the Stingray Add-in, or if you encounter difficulties when recording and running tests and business components on Stingray applications, you can use the options in this pane to fine-tune the configuration. For example, you can enable support for multithreaded applications by selecting the relevant option in this pane.

  After modifying this pane, you must restart OpenText Functional Testing before you continue working with this add-in.

• Clicking the Restore Factory Defaults button resets all product settings, including ALM connection information, the recent files list, and anything defined in the Options dialog box, such as startup options, UI layout, GUI, API, and BPT testing options, remote connection credentials, and more.

Set Up Your Stingray project using the Precompiled Agent mode

Instructs OpenText Functional Testing to support multithreaded Stingray applications. If you are not sure whether you are working with a multithreaded Stingray application, first try to record and run on your Stingray application without selecting this checkbox. If you experience difficulties, you can select this checkbox and try again.

Select this checkbox only if you are working with a multithreaded application.

Instructs OpenText Functional Testing to use auxiliary caching as a backup for MFC's internal mapping of window handles to Visual C++ objects. If OpenText Functional Testing cannot identify one or more Stingray controls while recording or running a test or business component, you can select this checkbox to instruct OpenText Functional Testing to use a cached map instead of using the Stingray application for identification.

Instructs OpenText Functional Testing to use the formatted data value in the Stingray grid control. You can use this option when working with table checkpoints (not supported for business components). For example, if the actual value of a cell in a Stingray application is formatted to display two digits to the right of the decimal point, OpenText Functional Testing will use that rounded number instead of the actual number when checking the value during the run session.

Instructs OpenText Functional Testing to record typing operations in a Stingray grid (edit) cell using one of the following options:

• WinTable.SetCellData statements. (Default) Uses the SetCellData method to record the final value that you enter in a grid cell. This option results in a single step in your test or business component. In most cases, this option makes the step more readable and easier to modify manually
• WinEditor statements. OpenText Functional Testing records each operation that you perform in a Stingray grid edit cell as a separate WinEditor step. For example, operations such as placing the cursor in a specific place in the edit box, typing a single character, or deleting a character may be recorded as individual steps. This can make your test or business component less readable and more difficult to modify manually, but this may be useful if you want to test the behavior of specific editing operations.

Instructs OpenText Functional Testing to treat the applications you specify as non-Stingray applications.

Some open, non-Stingray processes (such as explorer.exe) can cause unexpected behavior when recording and running tests and business components on Stingray applications. By adding the process names to this edit box, you can help prevent this unexpected behavior.

• In some cases, the executable file you use to open an application is only a launching process, which then opens the actual application process. In these cases, make sure that you specify the name of the actual application process and not the launching process.

• When working with tests, this option is relevant only if you selected the Record and run test on any open Windows-based application in the Record and Run Settings dialog box (Record > Record and Run Settings). For details on the options available, see Windows Applications Tab (Record and Run Settings Dialog Box).

Indicates the versions of the Stingray Objective Grid and Stingray Objective Toolkit libraries used for identifying Stingray objects in your application (read-only).

Opens the Stingray Support Configuration Wizard, which enables you to select the combination of Objective Grid and Objective Toolkit versions with which you want to work.

For details, see Stingray Support Configuration Wizard.

Instructs OpenText Functional Testing to generate a diagnostic agent log file. You can use this option if you encounter problems with the Stingray Add-in, for example, if OpenText Functional Testing does not recognize a Stingray grid control while recording. OpenText Software Support may ask you to generate this log and send it together with your service request.

When you select this checkbox, the following options are enabled:

• Include detailed log information for this control

• Log file (C:\st_agent.log)

• External debug application

If you select this checkbox, you must specify the location for the generated log. For details, see Specify location(s) for the generated log.

Instructs OpenText Functional Testing to include detailed information in the generated log for a specific Stingray control, in addition to the general OpenText Functional Testing/agent communication log information. For example, you may want to generate additional log details for a specific Stingray grid.

To select the object for which you want to generate detailed log information:

Click the pointing hand and then click the relevant Stingray control. The selected object's window handle is displayed in the edit box.

This option is available only when the Generate diagnostic agent log checkbox is selected.

Instructs OpenText Functional Testing to generate the log to the selected locations. You can select one or both of the following options:

• Log file (C:\st_agent.log). Saves the diagnostic log to the st_agent.log text file on your C: drive.

• External debug application. Exports the diagnostic log data to an external debug application, such as the freeware application, DebugView, or Microsoft VisualStudio.

These options are available only when the Generate diagnostic agent log checkbox is selected.