Known Issues - Oracle Add-in

This section contains general information and limitations about the Oracle add-in.

Installation
  • If you install an Oracle JInitiator 1.1.x version after you install the UFT Oracle Add-in, you must repair UFT to test applications running in the newly installed JInitiator version.

    Note: It is not necessary to re-install or otherwise configure the UFT Oracle Add-in if you installed a new Oracle environment other than JInitiator 1.1.x.

  • If the Java console does not display a line containing text similar to: Loading Oracle Support, check that the settings in your environment correspond to the environment settings defined in this section, or check for a batch file that may override the settings.

  • If your Java console displays the line Could not find –Xrun library: jvmhook.dll, check that you have jvmhook.dll in your system folder (WINNT\system32, Windows\System32, or Windows\SysWOW64, depending on your operating system).

Object identification

Test objects that require the index property for their description (for example, range flexfield objects) cannot be created from the Active Screen.

Workaround: Use the Add Objects button in the Object Repository window to add these test objects directly from your Oracle Applications instead.

Recording
  • The Log out of the application when the test closes option in the Record and Run Settings dialog box does not work if the Responsibilities List of Values window is displayed in the Oracle Applications session.

  • Active Screen captures are not supported for OracleListOfValues and OracleNotification test objects.

  • When recording on an Oracle ADF application on Internet Explorer, UFT recording may experience unexpected behavior or poor performance.

    Workaround: Record on Chrome or manually create the test steps.

Running tests on Oracle applications
  • The recovery scenario pop-up window trigger event is not supported when testing Oracle Applications.

  • Simultaneous testing of multiple Oracle Applications sessions is not supported.

Checkpoints
  • Performing a checkpoint on an object that is not always visible (such as a list opening from a combo box selection or a menu item) is not fully supported.

    Workaround: If a checkpoint on a transient object is required, make sure the object is visible prior to executing the checkpoint. For example, in the case of combo box list, you should insert a statement that clicks the combo box button before executing the checkpoint.

  • When testing Oracle applications, a table checkpoint may not capture the values of columns that are not visible.

    Workaround: Before creating a table checkpoint, scroll in the table so that the last column is visible.

Oracle Forms 12c

The following limitations apply when running Oracle Forms 12c applications:

  • The OracleCalendar test object is not supported.

  • Picklist controls are not supported.