Home
Troubleshooting
This guide describes how to analyze and resolve some of the common problems that you might encounter while you work with Rational® Functional Tester.
Troubleshooting in the Functional Test perspective
In this section, you will learn how to troubleshoot the tests in the Functional Test perspective.
Collecting Rational® Functional Tester error logs
While working with Rational® Functional Tester, you might encounter some problems that you can easily troubleshoot. If you are unable to troubleshoot the problem, you can contact IBM Software Support. Gather all the required background information such as logs, crash dumps, and traces and provide them to the IBM Software Support for investigation. In addition to the background information, you must also generate the error logs and provide those files to the support team.

Troubleshooting
This guide describes how to analyze and resolve some of the common problems that you might encounter while you work with Rational® Functional Tester.
- Troubleshooting in the UI Test perspective
  In this section, you will learn how to troubleshoot the tests in the Web UI Test perspective.
- Troubleshooting in the Functional Test perspective
  In this section, you will learn how to troubleshoot the tests in the Functional Test perspective.
  - Troubleshooting functional tests in Mozilla Firefox browsers
    If you encounter problems while testing in Mozilla Firefox browsers, the following workarounds might help resolve them.
  - Unable to test eclipse-based applications
    Generally the applications that are enabled for functional testing is in the enabled state after you upgrade Rational® Functional Tester. If you find any issues while testing the applications, disable the Eclipse application and enable it again for functional testing.
  - Ambiguous object recognition in functional testing
    Ambiguous recognition occurs when Rational® Functional Tester can not uniquely identify an object in the system-under-test. This commonly happens when Rational Functional Tester cannot differentiate between an instance of the application-under-test started by a script playback and an instance of the same application inadvertently left open previous to script playback. This also applies to identical windows from one application and identical HTML documents. Ambiguous recognition will cause script playback failure unless the duplicate application is closed.
  - Screen snapshot on playback failure of functional tests
    If playback of a script causes an exception to be thrown, Rational® Functional Tester takes a screen snapshot at the time of the failure. The screen snapshot is accessible through the log.
  - Tips and tricks for functional testing HTML applications
    This topic provides tips and tricks for recording and playing back scripts to test HTML applications.
  - Java applets in HTML pages
    You can test Java™ applets within a browser (Firefox, Internet Explorer). Java applets are not mapped as nested within HTML but are recorded as top-level objects. In the test object map, applets appear at the top level.
  - Standard properties available for functional testing HTML objects
    Standard properties provide a common way to access properties and their values across browsers. This topic lists the standard properties available for HTML objects.
  - Uninstalling Rational® Functional Tester cleanly
    If you have any issues during uninstall and reinstall of Rational® Functional Tester, you can perform a few tasks to verify whether the required processes are stopped and all the files are deleted from the computer.
  - Problems with object recognition
    If you encounter a problem with object recognition during testing, you might be able to resolve the problem by following these instructions.
  - Troubleshooting issues in SAP tests
    You can find information about the issues or problems that you might encounter while you test the SAP GUI. Details about issues, their causes and the resolutions that you can apply to fix the issues are described in the following table.
  - Problems with environment enablement
    When it is not possible to record on the application-under-test, you must verify whether the test environment was enabled for functional testing.
  - Handling exceptions
    If an exception occurs during testing, you might be able to handle it by following these instructions. Two common exceptions are the ambiguous recognition exception and the Mutex timeout exception during playback.
  - Collecting Rational® Functional Tester error logs
    While working with Rational® Functional Tester, you might encounter some problems that you can easily troubleshoot. If you are unable to troubleshoot the problem, you can contact IBM Software Support. Gather all the required background information such as logs, crash dumps, and traces and provide them to the IBM Software Support for investigation. In addition to the background information, you must also generate the error logs and provide those files to the support team.
  - Viewing trace files within Rational® Functional Tester
    You can view Rational® Functional Tester trace files in the Rational Functional Tester integrated development environment (IDE) Error Log view.
  - Frequently asked questions
    This section provides answers to frequently asked questions about IBM® Rational® Functional Tester.
  - Rational® Functional Tester error messages
    This section provides information about error messages that you might encounter with Rational® Functional Tester. This section lists the error messages by ID, explanation, system action and your response to correct the error message.

Collecting Rational® Functional Tester error logs

While working with Rational® Functional Tester, you might encounter some problems that you can easily troubleshoot. If you are unable to troubleshoot the problem, you can contact IBM Software Support. Gather all the required background information such as logs, crash dumps, and traces and provide them to the IBM Software Support for investigation. In addition to the background information, you must also generate the error logs and provide those files to the support team.

About this task

To generate Rational® Functional Tester error logs:

Procedure

Set the preferences for logging and tracing in the Logging and Tracing page. Click Window > Preferences, expand Functional Test in the left pane, and then click Logging and Tracing. You can collect the errors, warning, and information messages into a log file (rft_log.txt). The debug information is collected as trace date into the trace file. The trace file can be either a .txt file or a .log file, depending on your specification in the Logging and Tracing page. Trace files in the .log format can be imported into the Eclipse Error Log view within Rational® Functional Tester for viewing and filtering. You can specify the log file and the trace file directory.
Perform the operation that caused the problem.
You can send the generated rft_log.txt and rft_trace.txt or rft_trace.log files to IBM Software Support.

Note: You can identify the files by looking at the timestamp of the generated files.