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 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.
Working in non-GUI mode
You can use the tools and executable files that are provided along with the product software. You can use these tools to perform different test actions in a non-GUI mode.
Running tests
Use Rational® Integration Tester to run tests with command-line and Ant APIs.

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 IBM® Rational® Integration Tester.
- Getting Started
  This guide provides an overview and describes the tasks to get you started with Rational® Integration Tester.
- Administrator Guide
  This guide describes how to install Rational® Integration Tester. 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.
    - Integration 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. This guide is intended for Integration testers.
    - Extending Rational® Integration Tester functionality by using custom functions
      You can add more calculations and operations to tests by using the Rational® Integration Tester custom function class. Rational Integration Tester custom function is a Java™ class that extends the com.ghc.ghTester.expressions function.
    - Working in non-GUI mode
      You can use the tools and executable files that are provided along with the product software. You can use these tools to perform different test actions in a non-GUI mode.
      - Command-line interfaces
        Rational® Integration Tester command-line client is available in Rational Integration Tester 8.0.1 or later.
      - Ant tasks
        Support for the environment, scenario and stub Ant tasks is supplied with Rational® Test Control Panel.
      - REST services
        Representational state transfer (REST) is a simple stateless architecture that generally runs over HTTP. When used in conjunction with IBM® Rational® Test Control Panel, HTTP methods (such as GET and POST) are mapped to actions on domains, environments, scenarios, stubs and other resource types.
      - Running tests
        Use Rational® Integration Tester to run tests with command-line and Ant APIs.
        Run tests by using the command line
        You can run tests by using the Rational® Integration Tester command line.
        Run tests by using an Ant task
        You can execute tests by using the Rational® Integration Tester Ant tasks.
        Exit codes returned by RunTests command
        The RunTests command returns different exit codes depending on success or failure.
      - Managing test results
        Use IBM® Rational® Test Control Panel to manage test results with command-line APIs.
      - Managing domains
        You can create, list, update, and delete domains with the Rational® Test Control Panel REST API.
      - Managing environments
        Locking a Rational® Test Control Panel environment prevents other users from changing the state of that environment, for example, starting or stopping stubs.
      - Managing scenarios
        Use IBM® Rational® Test Control Panel to manage scenarios with command-line, Ant, and REST APIs.
      - Managing stubs
        You can manage stubs by using the command-line, Ant, and REST APIs.
  - 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 (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 Rational® Integration Tester
  While working with Rational® Integration Tester, you might encounter some problems that you can easily troubleshoot.
- Rational® Integration Tester reference
  Rational® Integration Tester 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.

Running tests

Use Rational® Integration Tester to run tests with command-line and Ant APIs.

JUnit style output

JUnit style results output is available for test.

The junitDir option specifies the path to write a JUnit style report to on completion of the run. Here is an example of the contents of such a file.

<?xml version="1.0" encoding="UTF-8"?>
<testsuites disabled="0" errors="0" failures="0" name="PassSuite" tests="1" time="0.0">
<testsuite tests="1" disabled="0" errors="0" failures="0" time="0.204" id="0" name="Scenario">
<testcase classname="Tests.Pass" name="Pass-0000001" time="0.04">
<system-out>
[2021-02-19T11:37:49.124] Initializing...
[2021-02-19T11:37:49.126] Using environment: IBM
[2021-02-19T11:37:49.127] - - - - Starting main steps - - - -
[2021-02-19T11:37:49.130] Pass: This passes!
[2021-02-19T11:37:49.154] 1 iteration(s) completed successfully
Logging summary: Info (0), Warnings (0), Errors (0)
Overall status:SUCCESSFUL
</system-out><system-err></system-err></testcase></testsuite></testsuites>