Java application testing problems

When working with Java applications, you can encounter some problems. This section helps pinpoint and resolve some common problems that may occur when testing Java applets and applications.

Running another application/applet with the same settings

You can run another Java application or applet with the same settings as the one you are currently running to help determine whether you are encountering a general problem with the Java Add-in or an application-specific problem.

When running another Java application or applet, do the following:

  • Determine whether the application is a standalone application or an applet.

  • If the application is an applet, check the browser type.

  • If the applet is executed from a shortcut, execute another applet with the same command.

  • If the applet is executed from a batch file, copy the batch file and change only the class file that invokes the applet.

    If the classpath must also be changed, add only the new items needed. Do not remove any of the items from the original application or applet classpath.

Back to top

Java console does not display "Loading Java 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.

Back to top

A different application works but current application does not

First check whether you can record and run tests if you invoke the other Java applet or application using exactly the same settings.

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.

Back to top

Application does not function with Xincgc

Either remove the -Xincgc option, or run without dynamic transformation support.

Back to top

Java console reports "Could not find -Xrun library"

Check that the jvmhook.dll is located within your java.library.path.

Back to top

UFT One 2021 R1 or earlier: Java 6

The following known issues are related to using Java 6:

Back to top