Home
Rational® Integration Tester
Tester Guide
This guide describes the tasks that you can perform for testing various domains, technologies, and applications. To enable testing, you must configure and enable the environment for testing.
Technical Tester Guide
Typically, a user with the Integration Tester role is also responsible for performance testing. This guide lists all such topics.
Creating and running performance tests
This topic describes how to create, configure, and run performance tests.
Creating performance tests
A performance test is created within a HCL OneTest™ API project.

Rational® Integration Tester
- Release Notes
  This document contains information about What's new, installation, known issues, and contact information of IBM Support.
- System Requirements
  This document includes information about hardware and software requirements for HCL OneTest™ API.
- Getting Started
  This guide provides an overview and describes the tasks to get you started with HCL OneTest™ API.
- Administrator Guide
  This guide describes how to install HCL OneTest™ API. After you install the software, you can perform administration tasks such as configuration and integration of the product. This guide is intended for administrators.
- Tester Guide
  This guide describes the tasks that you can perform for testing various domains, technologies, and applications. To enable testing, you must configure and enable the environment for testing.
  - Integration Tester Reference
    This guide provides the topics to help the Integration tester use the product by using the user interface, commands or scripts. This guide is intended for Integration testers.
  - Technical Tester Guide
    Typically, a user with the Integration Tester role is also responsible for performance testing. This guide lists all such topics.
    - Creating and running performance tests
      This topic describes how to create, configure, and run performance tests.
      - Before creating performance tests
        Agents (HCL OneTest™ API Agent) are required on the computers that will run HCL OneTest API tests and the probes that monitor the systems.
      - Creating performance tests
        A performance test is created within a HCL OneTest™ API project.
        Execution
        Select the root of the performance test in the configuration tree to display its configuration details, as shown below.
        Configuring references
        You can configure a performance test to run scenarios, which are collections of stubs, that are available on the HCL Quality Server domain associated with your HCL OneTest™ API project.
        Configuring probes
        The Probes tab (on the Config tab) is used to configure which probes to run during the test, and where to run them.
        Adding distributed tests
        You can add distributed tests to a performance test.
        Log Measurement action (optional)
        With the Log Measurement action, you can periodically record custom data, that is, data that is not provided by test engines and probes, as a performance test runs. The recorded data is stored in a database and is used to generate performance charts. Each item of data that is recorded is called a counter. Attributes are used to identify the counters. A UTC time stamp is stored with each set of counters.
      - Performance tests
        Performance tests are executed in HCL OneTest™ API in the same way and from the same perspectives as any other test resource.
      - Troubleshooting: Running a performance test with a MySQL database
        You can troubleshoot an issue that you encounter while you run a performance test with a MySQL database.
    - View test results
      This topic describes how to work with __PTS_RR_NAME__ charts in the Results Gallery perspective.
    - Deploying probes
      A HCL OneTest™ API probe measures variables from a particular component in the system and reports back its findings for processing and storage.
  - Integration Tester Guide (Service Virtualization)
    This guide describes the tasks that you can perform for using virtual services or stubs to simulate parts of an environment if the real services are not yet available or because they are difficult or expensive to use. This guide is intended for Integration Testers.
- Test Manager Guide
  This guide describes the tasks that you can perform for tracking the quality of the application. This guide is intended for Test Managers.
- Troubleshooting HCL OneTest™ API
  While working with HCL OneTest™ API, you might encounter some problems that you can easily troubleshoot.
- HCL OneTest™ API reference
  HCL OneTest™ API is a scripting-free environment for developing tests for service-oriented architecture (SOA) messaging and business process integration projects. Tests can be built by recording existing system behaviors or from requirements, by entering the data to send and the data that is expected in return.
- 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 product documentation.

Creating performance tests

A performance test is created within a HCL OneTest™ API project.

About this task

To create a performance test:

Procedure

Right-click the required operation or folder and click New > Tests > Performance Test.
Alternatively, click the arrow next to the test icon at the top of the component tree and click Performance Test.
In the Create new Performance Test dialog box, enter a suitable name for the performance test (the tests results will be identified by this name).
Click OK.
The empty performance test is displayed in the design view, to the right.

The new test is displayed at the top of an empty tree under the Config tab. The tree is created as items are added to the test. When an item in the tree is selected, its details are displayed on the right panel. With nothing selected (right-click the empty space beneath the tree), some documentation about using the test editor is displayed.

Note: On the Documentation tab, you can enter a description of the test and enter the name or user ID of the tests owner.

What to do next

If the test does not have any timed sections, when you run the test, the status messages will neither report the pass or fail progress nor report any values for passed, timed out, and failed parameters. To prevent this problem, add a timed section around your test steps in the test sequence. See Timed sections.