Home
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
Many test actions can be completed in non-GUI mode by using the command line, Ant, or REST interfaces.
Running tests
Use Rational® Integration Tester to run tests with command-line and Ant APIs.

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
    Many test actions can be completed in non-GUI mode by using the command line, Ant, or REST interfaces.
    - 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.
- 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.

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"?>
<testsuite failures="0" name="Tests/Suite" tests="1" time="1.594">
   <testcase classname="Tests/Test" name="Test" time="1.261"/>
</testsuite>