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.
Integration Tester Guide
Typically, a user with the Integration Tester role is also responsible 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 tester is also interested in reports, results and statistics for their testing. This guide lists all such topics.
Publishing and running stubs
You can publish stubs that are created in HCL OneTest™ API to HCL Quality Server, Dockerfile and build context, Kubernetes, or Istio, if the stub is based on a supported transport.
Running stubs
Several methods are available to start and stop the stubs. You can also modify and control stubs while they are running.
Starting stubs
HCL Quality Server, HCL OneTest™ API, Docker, or IBM Cloud Private can be used to start stubs.

Rational® Integration Tester
- Release Notes
  This document contains information about What's new, installation, known issues, and contact information of IBM Support.
- Integration Tester Guide (New user)
  Typically, a user with the Integration tester role is responsible for certain tasks including creating and running tests and virtual services to determine the quality of the API layer of the system. This guide lists all such topics to help the new Integration tester get started with the product.
- Administrator Guide
  Typically, a user with the administrator role is responsible for certain tasks including installation, configuration, and integration of the product. This guide lists all such topics.
- 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
    Typically, a user with the Integration Tester role can work in the user interface, use commands or scripts. This reference lists all such topics to help the Integration Tester use the product.
  - Technical Tester Guide
    Typically, a user with the Integration Tester role is also responsible for performance testing. This guide lists all such topics.
  - Integration Tester Guide
    Typically, a user with the Integration Tester role is also responsible 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 tester is also interested in reports, results and statistics for their testing. This guide lists all such topics.
    - HCL OneTest™ Virtualization overview
      HCL OneTest™ Virtualization is software that is used for creating, maintaining, publishing, and running message-based stubs and database stubs.
    - Task flow: Working with the HCL Quality Server Environments dashboard
      You can use the HCL Quality Server Environments dashboard to perform various tasks such as starting, stopping stubs and scenarios, and modifying stub configurations after you have published stubs to HCL Quality Server. You can also lock the environment that contain the published stubs.
    - Virtualizing HTTP
      You can simulate an HTTP connection with a virtual service, also known as a stub.
    - Virtualizing HTTPS
      You can simulate an HTTPS connection with a virtual service, also known as a stub.
    - Virtualizing TCP
      You can simulate a TCP connection with a virtual service, also known as a stub.
    - Virtualizing a REST API without recording or synchronization
      You can virtualize REST APIs by using the Recording Studio, or by synchronizing WADL, Swagger, or RAML documents. When none of these options is available, you can still manually virtualize REST APIs that use path parameters.
    - Creating message-based stubs
      In HCL OneTest™ API, there are several methods that you can use to create a message-based stub.
    - Modifying message-based stubs
      You can use either the Test Editor or the Stub Editor to create, modify, and enhance any legacy or new stubs created by HCL OneTest™ API.
    - Creating and modifying database stubs
      You can create and modify database stubs in HCL OneTest™ API.
    - Configuring stubs to connect to HCL Quality Server and the HTTP proxy
      A stub running on its own may not be sufficient in some cases, because it might have dependencies on services such as HCL Quality Server or the HTTP proxy. If the stub is running on the public cloud and the services are running in the enterprise, you must configure the stub to connect to these services.
    - Publishing and running stubs
      You can publish stubs that are created in HCL OneTest™ API to HCL Quality Server, Dockerfile and build context, Kubernetes, or Istio, if the stub is based on a supported transport.
      - Publishing stubs
        You can publish a stub to HCL Quality Server, Dockerfile and build context, Kubernetes, or Istio with Kubernetes by using the HCL OneTest™ API Publish Stubs wizard.
      - Running stubs
        Several methods are available to start and stop the stubs. You can also modify and control stubs while they are running.
        Starting stubs
        HCL Quality Server, HCL OneTest™ API, Docker, or IBM Cloud Private can be used to start stubs.
        Starting stubs: HCL Quality Server method
        If you cannot use, or do not have access to HCL OneTest™ API to control stubs that were created and published from HCL OneTest API, use the Environments Dashboard of HCL Quality Server to start the stubs.
        Starting stubs: HCL OneTest™ API method
        HCL OneTest™ API can be used to start stubs, but HCL Quality Server provides more control over the startup of a stub or a set of stubs.
        Running stubs in a Docker container
        After you publish one or more stubs to a Dockerfile and build context and you built a Docker image from those files, you use the docker run command to run the image in a container.
        Running stubs in Istio or Kubernetes
        After you publish one or more stubs to Istio or Kubernetes, you must upload the project files to a file server and edit the YAML file to point to the URL of the file server before you can run the stubs.
        Scenarios
        In HCL Quality Server, you can create scenarios, which are collections of configured stubs that can be started and stopped together.
        Stopping stubs
        You can use HCL Quality Server, HCL OneTest™ API, or Docker to stop the stubs.
      - Modifying running stubs
        If you are using HCL OneTest™ API to run a stub, you can modify the stub while it is running.
      - Controlling running stubs
        You can control stubs that are running in a number of ways.
      - Behaviors for stubs
        You can create a simple behavior called "echo" that will expose one function and one event for use by a HCL OneTest™ Virtualization stub.
    - Viewing results in HCL Quality Server
      You can use HCL Quality Server to display the results of tests that you run in both HCL OneTest™ API and HCL Quality Server.
    - Viewing usage statistics of virtual services in HCL Quality Server
      You can use HCL Quality Server to display the usage statistics of virtual services across HCL OneTest™ Virtualization and HCL OneTest API.
    - Viewing reports in HCL OneTest™ Server
      All the project stakeholders can view test reports for multiple testing products from the Results page on HCL OneTest™ Server. You can access the Results page from a web browser. Therefore, there is no need to install the desktop client.
    - Troubleshooting: HCL OneTest™ Virtualization
      You can use workarounds to common problems that you might encounter when you use HCL OneTest™ Virtualization.
- Test Manager Guide
  Typically, a user with the Test Manager role is responsible for certain tasks that includes tracking the quality of the application. This guide lists all such topics.
- 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.

Starting stubs

HCL Quality Server, HCL OneTest™ API, Docker, or IBM Cloud Private can be used to start stubs.

There are some limitations on stubs depending on how they are started. The following table describes those limitations.


If a stub is published to HCL Quality Server and started by HCL Quality Server...	If a stub is started by HCL OneTest™ API...	If a stub is published to a Dockerfile and build context and an image built and run by Docker...	If a stub is published to IBM Cloud Private resource files (Kubernetes) and a resource created and run by IBM Cloud Private...
There are no running time limits on the stub.	It will run for only 5 minutes unless the associated test scenario requires it to run for a longer period.	There are no running time limits on the stub.	There are no running time limits on the stub.
There are no transactions per second (TPS) limits on the stub.	There is a limit of 1 TPS on the stub.	There is a limit of 10 TPS on the stub.	There is a limit of 10 TPS on the stub.

The following topics describe how to use HCL Quality Server, HCL OneTest™ API, Docker, or IBM Cloud Private to start stubs.