If the Could not create the Java Virtual Machine error message is displayed, activate OpenText Functional Testing's memory defragmenting by adding a line to the mercury.ini file.

Locate the mercury.ini file in your Windows folder (%windir%) and add a line to the Memory_Defrag section, as follows:

[Memory_Defrag] <process_name>.exe=1

where <process_name> is the name of the Java engine or application that you are using.

To turn off defragmenting, change the 1 value to 0.

If no error message appears, and Eclipse fails to start with higher memory settings, do one of the following:

• Use a 64-bit Windows operating system and 64-bit JVM, with 64-bit Eclipse.

  Having a 64-bit virtual memory space can prevent you from encountering memory fragmentation issues.

• Force Eclipse to start using the java.exe or javaw.exe file instead of the default startup file.

  To do this edit the eclipse.ini file by adding the following text, on two separate lines:

  -vm

  <full path to the java.exe or javaw.exe file>

• Modify the Eclipse memory setting in the eclipse.ini file.

  For example, if the application fails to start with a parameter setting of -Xmx512m, use a parameter setting of -Xmx256m or -Xmx384m instead.

When launching an application on a computer using Java version 8, if you:

• Launch an Oracle Forms application or Java applets over Java jre8u91
• JavaFX applications over Java jre8u45

OpenText Functional Testing returns a "VerifyError" error.

Workaround: Add -UsesplitVerifier to the runtime parameters in the Runtime environment settings.

Adding a -Xincgc flag to the java.exe command line prevents the Java support from working properly.

You might do this in the Record and Run Settings dialog box, or in a batch file.

Workaround:

When testing with OpenText Functional Testing Java support, do not use -Xincgc in your command line, or, alternatively, do not use the dynamic transformation support mechanism.

When selecting a JAR file from the command line in the Record and Run Settings dialog box, you should manually add -jar to the Command line box before you invoke the Java application.

If you intend to launch your Java application using the Record and Run Settings dialog box without using a batch file (or another executable file), and without the -jar command line option (after selecting a JAR file), you should include the fully qualified name of the Java class in the Command line box.

If, while recording keyboard operations in a JFC single-line edit box in an IME composition window, you press the ENTER key to select the composition string, the key press may be recorded as the Activate method, thereby generating an extra step. For example:

JavaWindow("Application").JavaEdit("User Name").Activate

This extra step generally does not affect the run session adversely.

Workaround:

Before running your test or business component, remove the extra step that was recorded.

The ALT+F4 keyboard shortcut is not supported for recording or running.

This shortcut is used used for closing a Java applet or Java application

Workarounds:

• Use a Close menu command or button to close a Java applet or Java application during a recording session.

• Manually add a JavaWindow(...).Close step.

By default, moving and resizing of Java windows are not recorded. This is because it may cause redundant recordings in some cases.

Workaround:

To instruct the Java Add-in to record these actions, use the Setting.Java method to set the record_win_ops variable to 1.

For example:

Setting.Java("RECORD_WIN_OPS") = 1

AWT popup menus are recorded by the Standard Window control support WinMenu test object, instead of the usual JavaMenu test object.

You cannot perform checkpoints or Active Screen operations on such menus.

Workaround:

Use other verification methods (such as using GetTOProperty).

The Java Add-in does not record or run steps for hovering over identifiers in an Eclipse window.

When you record a step that closes a Java dialog box, OpenText Functional Testing records an additional Close statement.

Workaround:

Manually delete the extra Close statement.

When the Active Screen displays a Java applet or ActiveX control within a Web page, the applet or control is for viewing purposes only and you cannot perform operations on the object.

For example, creating checkpoints or adding methods.

Workaround:

Record an operation on the Java applet/ActiveX control to create a step on the object with the ActiveX Add-in and/or Java Add-in loaded.

Then you can create a checkpoint, parameterize a step, or add a method from the individual Java applet/ActiveX control in the Active Screen.

If you want to use a control's native property for object identification, you can add the property to a Java test object as an in the Add/Remove Properties Dialog Box dialog box. If you do this, consider the following:

• You can add only native properties for which the control has a public get or is method that returns the property value.

• If the native property name includes upper-case letters, then in the corresponding name that you create, you must replace each of the upper-case letters except the first one with _<lower-case letter>.

  For example, to use the native property OneSmallProp, add an named One_small_prop.

In early releases of QuickTest, Java description properties were not case-sensitive.

If you learned a test object in a QuickTest version earlier than 11.00, you need to re-learn the object with properties that are case-sensitive by performing an Update Run.

Do this using the Update test object descriptions option.

You cannot add SWT-based JavaMenu objects directly to an object repository using the Add Objects to Local button in the Object Repository window, or the Add Objects button in the Object Repository Manager.

If you want to add an SWT-based JavaMenu objects to the object repository, you can:

• Add the parent object and select to also add the descendants.

  Use the Add Objects or Add Objects to Local button.

• Add a JavaMenu object using the Navigate and Learn option in the Object Repository Manager.

Scroll bar controls in AWT and Swing applications are represented by JavaSlider test objects.

Scroll bar controls in SWT applications are not supported.

Scroll bar controls in JavaFX applications are supported, represented by JavaSlider test objects.

A call to .Object.startModal of a JavaInternalFrame or JavaDialog object may cause OpenText Functional Testing to behave unexpectedly until the dialog box is closed.

The use of multi-byte characters in a multiline edit field object is not supported.

For button objects whose label is determined by the name of the image file they display, the process of naming the test object when running in JDK 1.6 and later is different than the one used when running in JDK 1.5. This applies to both JavaButtons or buttons in a JavaToolbar.

Therefore, if you have a test or business component containing button objects that were learned on JDK 1.5 and labeled according to their image file, when you run it on JDK 1.6, the test or business component may fail.

Workaround:

• For a JavaButton object—relearn the object on JDK 1.6 or later.

  Then modify the test to use the new test object, or delete the old object from the object repository and rename the new test object to match the object name used in the step.

  Make sure the Automatically update test and business components steps when you rename test objects option is selected in the General pane of the GUI Testing tab in the Options dialog box (Tools > Options > GUI Testing tab > General node).

• For a button in a JavaToolbar object, modify the Item argument in the JavaToolbar statement to refer to the relevant button.

  Specify the button's index, or use the Object Spy to spy on the toolbar button, and then provide the label as the Item argument.

The PropertyValue argument (second argument) of the WaitProperty method for any Java test object can be only of type string.

Workaround:

Use a string instead of the original type.

For example, instead of 1, use "1".

y = JavaCheckBox("Active").WaitProperty ("enabled", "1", 1000)

You can create text checkpoints and text output values only for Java objects that meet specific criteria. For details, see Text checkpoint/output value steps for Java objects.

To create a new table checkpoint on a Java table while editing a test or business component, you must first open the application containing the table you want to check and display the table in the application.

If you add a checkpoints on a JavaList or JavaTree object while editing a test or business component, the list_content or tree_content property is not available in the checkpoint.

Workaround:

Create checkpoints on Java lists and Java trees while recording.

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 working with tests, if you create a checkpoint on an SWT-based Java tree with columns, a table checkpoint is created.

To record the CloseTab method on a tab item in a JavaFX application, you must first select the tab item.

The OpenText Functional Testing test can close only the selected tab. It cannot close all tabs in one step.

The display scaling must be set to 100% for OpenText Functional Testing to identify objects in JavaFX applications.

Setting the scaling to 125% or 150% may cause OpenText Functional Testing to recognize objects as Standard Windows objects instead of Java.

The following methods are not supported for JavaFX objects:

• Object.getText
• JavaCalendar.GetTime

• Browser dialog boxes (like Alert, Confirm, and Prompt dialogs)

• Modal or modeless dialog boxes

• Cross-domain frame/iFrame objects

• Web applications design with Web 2.0 toolkits (ASP .NET AJAX. Dojo, Google Web Toolkit, jQueryUI, EXT-JS, Siebel Open UI, and Yahoo UI)

• Browser operations

• Navigate and Learn

• Drag and Drop

• Active Screen

• Recording on Frame or iFrame objects

• Recording on role-based controls (that use the role= property)

• Options in the Web > Advanced pane of the Options dialog

• All Browser test object methods

• WebFile objects

• ViewLink objects

• WebXML objects