While working with IBM 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 and
provide the details 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
IBM Rational Functional Tester error
logs:
Procedure
- Close IBM Rational Functional Tester.
- Open the ivory.properties file, and modify the following
parameters. This file is available at: Functional
Tester installation directory\Functional Tester\bin\
- To enable debugging, set the following flags to true:
- rational.test.ft.debug.enabled=true
- rational.test.ft.debug.native_to_file=true
- To generate a more detailed debugging report, change
the rational.test.ft.debug.filter=default,1; to default,3
- Optional: Specify the name and location
of the debug file by modifying this parameter rational.test.ft.debug.filename=C:/ivDebug.txt . By default, the ivDebug.txt file is generated in the C:\ directory.
- Save the ivory.properties file.
- Optional: Open IBM Rational Functional Tester. You can collect the
errors and warning messages into a log file (rft_log.txt). Similarly,
you can collect debug information as trace data into a trace file
(rft_trace.txt). To set the preferences for logging and tracing through
an user interface; click . In the left pane,
expand Functional Test and click Logging
and Tracing.
- Open IBM Rational Functional Tester,
if not already open, and perform the operation that caused the problem.
- Send the generated ivDebug.txt file to IBM Software Support.
- Optional: You can also send the generated rft_log.txt,
and rft_trace.txt files along with the ivDebug.txt file to IBM Software
Support.