Home
Test Manager guide
As a test manager, you can 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 Web UI Test perspective
In this section, you will learn how to analyze test results in the Web UI Test perspective.
Evaluating desktop web UI results
After the test run, Unified Reportthe 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.
Low Intensity Performance Testing
In performance testing, the user load is gradually increased from low intensity to high intensity. Testing the performance of the application with very few users is referred to as Low Intensity Performance Testing. Typically, you require performance test assets to do performance testing. However, in IBM® Rational® Functional Tester, you can do functional testing and low intensity performance testing with the same functional test assets.
Adding a transaction
A transaction is a business scenario in the application under test such as logging in, checking out a product, or making a payment. It is a logical grouping of certain UI actions. You add a transaction to the test to check the performance for the entire transaction rather than each UI action in the transaction.

Test Manager guide
As a test manager, you can 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 results to the server
  The test results indicates the quality of application under test. Different stakeholders to the application might want to check the quality of application but do not have the workbench or desktop client installed. As a desktop client user, you 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 yet published to IBM® Rational® Test Automation Server, you can publish all of them simultaneously.
- Unified reports
  The unified reports in Rational® Functional Tester provide a detailed overview of the test results. The unified reports provide an extensive user interface that you can use to analyze or apply filters on the test results.
- Results for tests in Web UI Test perspective
  In this section, you will learn how to analyze test results in the Web UI Test perspective.
  - Mobile and Web UI Statistical report
    Use this report to view the performance data for your application. The 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 Reportthe 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.
    - UI Test live report
      When you initiate a test run, the Test Execution perspective displays the UI Test report. This report shows the status of each step that is being currently running on the browser. After the test run completes, the UI Test Report shows up in a new tab.
    - Generating Functional Test Report
      To create an HTML report that can be printed or used outside of the workbench, generate a functional test report. The functional test report shows the verdicts for the test and for each step of the test. Functional reports are generated from the test run as HTML files that use predefined report designs.
    - Low Intensity Performance Testing
      In performance testing, the user load is gradually increased from low intensity to high intensity. Testing the performance of the application with very few users is referred to as Low Intensity Performance Testing. Typically, you require performance test assets to do performance testing. However, in IBM® Rational® Functional Tester, you can do functional testing and low intensity performance testing with the same functional test assets.
      - Adding a transaction
        A transaction is a business scenario in the application under test such as logging in, checking out a product, or making a payment. It is a logical grouping of certain UI actions. You add a transaction to the test to check the performance for the entire transaction rather than each UI action in the transaction.
      - Defining performance requirements in transactions
        You can define performance requirements for transactions in a test. These requirements specify acceptable thresholds of performance for transactions and validate service level agreements.
    - Viewing On App and Off App response time
      When you initiate a test run from the test workbench, by default, the response time is collected and displayed in the Mobile and Web UI Report after the run. This report shows the overall response time for each test step. The response time is also displayed on the Step Performance tab of the statistical report. This report shows the average response time for 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.
- Results for tests in Functional Test perspective
  In this section, you will learn how to analyze test results in the Functional Test perspective.

Adding a transaction

A transaction is a business scenario in the application under test such as logging in, checking out a product, or making a payment. It is a logical grouping of certain UI actions. You add a transaction to the test to check the performance for the entire transaction rather than each UI action in the transaction.

About this task

You can add a transaction only for the Launch App or In App nodes. So, if you have a bunch of steps that justifies a transaction, split them from the rest of the steps to add a transaction.

Procedure

In the Test Navigator, browse to the test and double-click it. The test opens.
In the test editor, select one or more steps in the test script for splitting into one or more application nodes.
Right-click the selected steps, and then select Split Mobile actions or Web UI actions.
In the refactoring dialog box that opens, click Split and create containers. Ensure that Transaction is selected.
To add a transaction only for the selected steps, select the Create containers for selected nodes only option.
To add a transaction for all the nodes (Launch App and In App) in the test, select the Create containers for all group of nodes option.
Click Finish.
The group of steps are nested in the In App node which is also nested in a Transaction.

What to do next

After the test run completes, to view the Transaction report, in the Statistical report tab, select Transaction Report. To view information about each report, click the help icon.