While working with IBM® DevOps Test UI (Test UI), 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.
To generate Test UI error
logs:
- Set the preferences for logging and tracing in the Logging
and Tracing page. Click , 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 Test UI 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.