Home
Rational® Functional Tester
Test Manager Guide
This guide describes how to keep track of the performance of the application by evaluating the test results. Following topics cover how you can work with the test results.
Results for tests in UI Test perspective
In this section, you will learn how to analyze test results in the Web UI Test perspective.
Logs overview
Rational® Functional Tester uses logs to store different types of information, which you can use to determine the reason for a test failure.
Test log overview
The test log contains a historical record of events that occurred during a test run or a schedule run, as well as the status of each verification point.

Rational® Functional Tester
- Release Notes
  This document contains information about what's new, installation instructions, known problems in and contact information of IBM Customer Support.
- System Requirements
  This document includes information about hardware and software requirements for IBM® Rational® Functional Tester.
- Getting Started Guide
  This guide provides an overview of Rational® Functional Tester. You can find the task flows to get you started with Rational Functional Tester. This guide is intended for new users.
- Tutorials
  You can learn to start using Rational® Functional Tester by reviewing the information in the Tutorials for the UI Test perspective and Functional Test perspective.
- Samples
  You can find the sample project that you can use with Rational® Functional Tester to test the functionality of an application.
- Administrator Guide
  This guide describes how to install IBM® Rational® Functional Tester software. After you install the software, you can perform administration tasks such as license configuration and integration with other products. This guide is intended for administrators.
- Test Author Guide
  This guide describes how to create test scripts and enhances them by applying different test elements such as dataset, variables, and verification points.
- Test Execution Specialist Guide
  This guide describes how to automate the playback of the tests by using different methods such as Docker, IBM Cloud Private, Jenkins and so on. The test results can be pushed to Rational® Test Control Panel.
- Test Manager Guide
  This guide describes how to keep track of the performance of the application by evaluating the test results. Following topics cover how you can work with the test results.
  - Publishing test result to IBM® Rational® Test Automation Server
    The test result indicate the quality of the application under test. There could be different stakeholders to the application who do not have the product installed but want to check the quality of application. You, as the user of the product, can publish the test result to IBM® Rational® Test Automation Server so that others can view it from the web browser.
  - Publishing specific results to the server
    If you have a single test result or multiple test results that are not published to IBM® Rational® Test Automation Server, you can publish a single or all of them simultaneously.
  - Unified reports
    Unified reports in Rational® Functional Tester provide a detailed overview of the test results.
  - Results for tests in UI Test perspective
    In this section, you will learn how to analyze test results in the Web UI Test perspective.
    - UI Test Statistical report
      You can use the UI Test Statistical report to view the performance data for your application. This report displays performance data for all of the transactions in the test, all of the steps in the test, and all of the supported computer resources.
    - Evaluating desktop Web UI results
      After the test run, Unified Report the statistical report, and test log is displayed. The statistical report displays response time data for transactions and test steps. The live report displays result for the functionality of each step and the test log shows details of each test step.
    - Customizing reports
      You can customize reports to specifically investigate a performance problem in more detail than what is provided in the default reports.
    - Export test results
      You can export the test result in different formats to share it with different stakeholders.
    - Evaluating mobile test run results
      To check whether or not the mobile test ran successfully, you can open the test report. You can also view each recorded functional action in the report.
    - Logs overview
      Rational® Functional Tester uses logs to store different types of information, which you can use to determine the reason for a test failure.
      - Test log overview
        The test log contains a historical record of events that occurred during a test run or a schedule run, as well as the status of each verification point.
      - Viewing test logs
        To see a record of all the events that occurred during a test run or a schedule run, as well as the status of each verification point, open the test log for that run. You can also compare an event from the test log with the request or response in the test to view the differences between the recording and the playback of the test.
      - Viewing errors while running tests
        To view errors and other events while a test is running, use the Execution Event Console view. If problems occur in a test run, you can examine the Execution Event Console view to determine whether to stop or continue the test.
      - Exporting test logs
        To process data from a performance test in another application or to use search tools to locate text in a test log, export the test log to a text file.
      - Exporting event log
        To view all the events that occurred during the run of a test from another file, you can export this data from the Event Log panel, to an XML, CSV, or text file.
      - Exporting event console output
        To view errors and other events of a test run from another file, you can export this data from the Execution Event Console view to an XML, CSV, or text file.
      - Setting problem determination level for tests
        You can set the level of information that is saved in the problem determination log during a run. By default, only warnings and severe errors are logged. Typically, you change this log level only when requested to do so by the Support person.
  - Results for tests in Functional Test perspective
    In this section, you will learn how to analyze test results in the Functional Test perspective.
- 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.
- Reference Guide
  This guide describes the additional topics to gain more knowledge about Rational® Functional Tester.
- All Guides (PDF)
  You can find the link to view or download the content of the release notes, system requirements, and persona guides of IBM® Rational® Functional Tester as a PDF file.
- Security Considerations
  You can take certain actions to ensure that your installation is secure, customize your security settings, and set up user access controls.
- Notices
  This document provides information about copyright, trademarks, terms and conditions for the product documentation.

Test log overview

The test log contains a historical record of events that occurred during a test run or a schedule run, as well as the status of each verification point.

About this task

The test log sets a verdict for each run as follows:

Pass indicates that all verification points matched or received the expected response and all the test steps successfully completed. For example, a response code verification point is set to PASS when the recorded response code is received during playback. If your test does not contain verification points, PASS means that all primary requests in the test were successful.
Fail indicates that at least one verification point did not match the expected response or that the expected response was not received or a Web UI step did not run successfully.
Error indicates one of the following results: a primary request was not successfully sent to the server, no response was received from the server for a primary request, or the primary request response was incomplete or could not be parsed.
The verdict is set to Inconclusive only if you provide custom code that defines a verdict of Inconclusive.

The verdict is rolled up from the child elements to the test level. For example, if a user group contains 25 virtual users, and five virtual users have failed verdicts, that user group has only one failed verdict, not five.