Known Issues - Stingray Add-in

This section describes troubleshooting and limitations for the Stingray Add-in.

General

  • Applying Stingray Support Configuration settings to all users on the computer has no effect on users that have opened OpenText Functional Testing at least once.

    Workaround: Apply Stingray Support Configuration settings separately for each user that has opened OpenText Functional Testing at least once.

  • OpenText Functional Testing does not support both Unicode and non-Unicode in the same application when the Stingray Add-in is loaded.

  • By default, only single-threaded Stingray applications are supported.

    To provide support for multithreaded applications, in OpenText Functional Testing, select Tools > Options > GUI Testing tab > Stingray node. Select the Support multithreaded Stingray applications checkbox and click OK. Close and restart OpenText Functional Testing.

  • If your Stingray application was built using the precompiled agent mode and you have used the Stingray Support Configuration Wizard at least once to set a Stingray run-time agent, then recording, learning, or running steps on the application may fail.

Back to top

Application objects

  • The Stingray Add-in does not support Objective Edit or Objective Chart controls.

  • By default, only the following grid classes are supported:

    • CGXBrowserView

    • CGXBrowserWnd

    • CGXGridWnd

    • CGXGridView

    • CGXGridHandleView

Back to top

Test objects and test object methods

  • The ExpandAll method is not supported for Stingray tree controls.
  • GetCellData and SetCellData methods are limited to 3000 characters.

Back to top

Object identification

  • When working with nested tab controls, you may need to manually modify the corresponding entries in the object repository to enable unique identification. For example, you may need to add an ordinal identifier to the existing description.

  • Sometimes, the MFC internal map that correlates a window handle of a control with the Visual C++ object may not contain an entry for all Stingray controls. In such cases, the Stingray Add-in may fail to recognize certain Stingray controls because it relies on this map when retrieving information from the application.

    Workaround: The Stingray Add-in contains an auxiliary mechanism that serves as a fallback for the lack of MFC map entries in the situation described above. To activate this mechanism, in OpenText Functional Testing, select Tools > Options > GUI Testing tab > Stingray node. Select the Cache MFC map checkbox and click OK. Close and restart OpenText Functional Testing.

    This mechanism is not activated by default because it imposes some performance overhead.

Back to top

Recording

  • By default, edit boxes, checkboxes, and drop-down (combo) lists are supported when recording on a Stingray grid. Other types of controls embedded in Stingray grids may be supported partially or may not be supported at all.

    The CGXTabbedComboBox control and the CGXCheckBoxEx control type are not supported during recording.

    Workaround: To work with controls other than the supported ones, manually add SetCellData statements to your test or business component (instead of recording user actions inside cells).

  • When Stingray tree control items have tooltips, recording the selection of an item by clicking its label may fail.

    Workaround: Select the requested item by performing a click on the item's icon.

Back to top