Home
Rational® Integration Tester
Reference Guide
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.
Test Factory
The Test Factory perspective is one of the main areas in Rational® Integration Tester. You can create all the tests and the required artifacts/data to support them.
Test Suites: Overview and tasks
A Test Suite represents a group of tests, test suites, and scenarios. Any combination of these items can be included, but a test suite must always contain at least one scenario and one test. Test suites are used mainly to construct reusable, packaged regression tests that can be run across multiple environments, or repeatedly within the same environment.
Test suite scenarios
In a test suite, a scenario controls how to execute the items it contains. A scenario can be added to a test suite.

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.
- 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
  While working with Rational® Integration Tester, you might encounter some problems that you can easily troubleshoot.
- Reference Guide
  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.
  - Rational® Integration Tester overview
    This section provides an overview of Rational® Integration Tester, including information about projects and files, the Rational Integration Tester user interface, environments, and project settings and preferences.
  - Architecture School
    Use the Architecture School perspective to build a system under test by using the logical, physical, and synchronization views. You can also use this perspective to manage the schemas available in your project.
  - Recording Studio
    With Rational® Integration Tester, you can record events (messages or database interactions) sent to and from the system under test. Use Recording Studio to control what parts of the system should be recorded. These parts could be specific parts of the system infrastructure or specific services using that infrastructure. You can then use the recorded events as a source of tests and other interactions with the system. In Recording Studio, you can record the traffic over a number of different transports.
  - Test Factory
    The Test Factory perspective is one of the main areas in Rational® Integration Tester. You can create all the tests and the required artifacts/data to support them.
    - Tests: Overview and tasks
      Tests are the fundamental building blocks of integration and SOA testing. A test sends an input message to an external service or system in a protocol-specific way and validates the reply against an expected result.
    - Test Suites: Overview and tasks
      A Test Suite represents a group of tests, test suites, and scenarios. Any combination of these items can be included, but a test suite must always contain at least one scenario and one test. Test suites are used mainly to construct reusable, packaged regression tests that can be run across multiple environments, or repeatedly within the same environment.
      - Manipulating the contents of a test suite
        Scenarios, test suites, and tests can be added to or removed from an existing test suite. They can be moved up or down within the scenario that contains them. Scenarios can be edited within a test suite. The item trees within a test suite can be expanded or collapsed. All of the test suite actions can be done by using the test suite toolbar or by right-clicking an item and using the menu.
      - Test suite scenarios
        In a test suite, a scenario controls how to execute the items it contains. A scenario can be added to a test suite.
        Scenario name and runtime options
        You can use the Config tab on the Scenario Editor dialog to configure the name and runtime settings for a test suite scenario.
        Scenario reference settings
        You can configure references or dependencies from the operations that are part of a test suite.
        Scenario data
        You can configure scenario data in the Data Drive tab.
        Scenario probes
        You can configure scenario probes in the Probes tab.
      - Results publishers
        To automatically publish the results of a test suite after it is run, use Results Publishers, which is created under Project Settings. Specify the publishers to use and the details of the results to publish and how to publish them on the Results Publishers tab.
      - The Continue on Fail option
        By default, all items in a test suite are executed when the suite is executed, regardless of whether previous items pass or fail. Depending on the nature of the tests it contains, however, the execution of a test suite can be terminated if one or more specific test items fail. This behavior is controlled with the Continue on Fail option, which can be set independently for each item in a suite.
      - Test Suite execution
        Test Suite execution can be initiated in the Test Factory, but the suite is run in the Test Lab perspective.
    - Stubs: Overview and tasks
      Stubs can be used to simulate services that you are unable to use or that are otherwise unavailable.
    - The Action Editor
      The Action Editor is used to modify the actions that are contained within a test or stub.
    - Creating a test template
      To save time when you are creating tests, you can create a template of test sequences that can be used to quickly create a number of pre-defined tests.
    - Test data sources
      You can configure test data sources that can drive a test template or a test by using several different instances of data. In this way, you can parameterize your tests, substituting specific data from a pre-configured source in different test iterations. You can also use test data to validate the results that are returned by different test actions.
  - Test Lab
    You use the Test Lab to execute test assets, repair tests, and open test assets for editing directly from this perspective. You can execute all of the tests, test suites, and stubs that are created in Test Factory.
  - Results Gallery
    You use the Results Gallery perspective to view an execution summary and detailed coverage, error, and performance reports for executed test suites and for test cases that were executed within a suite or as part of a test cycle.
  - Messages
    Rational® Integration Tester can publish and subscribe to messages as part of a test. A message normally consists of two parts: a header and a body. The header usually adheres to a predefined logical construction, while the structure of the body can be more arbitrary.
  - Schemas
    Rational® Integration Tester can handle many types of content. For the product to be able to interpret the variety of content types, it must associate a content format description, or schema with the content.
  - Database resources, connections, and bindings
    Rational® Integration Tester can interact with any database that supports connectivity through the JDBC specification. These interactions can be used to extract or update data where necessary, and test data sets can be taken directly from database table content.
  - Identity stores and SSL
    An identity store can group a collection of one or more certificates that can be used in IBM® Rational® Integration Tester to validate and authenticate connections that use SSL. After you create an identity store, you can use it to enable SSL communications in various messaging transports.
  - Scripting within tests and stubs
    You can use scripts in Rational® Integration Tester that include the Rational Integration Tester legacy scripting language, ECMAScript (such as JavaScript™), or any third-party scripting language that you install.
  - External tools
    Rational® Integration Tester is primarily GUI-based, but you can also run or view tests, suites, and stubs outside of the Rational Integration Tester.
  - Test actions
    Actions are the building blocks of a test. A test consists of a series of steps and each step is an action. Actions can be defined for tests and stubs.
  - Formatting and parsing date-time patterns
    For some fields in Rational® Integration Tester, you can define patterns for date-time formatting. Pattern letters are repeated, as their number determines the exact presentation of the date-time information that they represent.
  - The Add Numbers service
    The Add Numbers service, included with Rational® Integration Tester, provides a simple way to generate messages that you can observe with topology discovery or capture in Recording Studio.
- 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.

Test suite scenarios

In a test suite, a scenario controls how to execute the items it contains. A scenario can be added to a test suite.

You can copy scenarios from Rational® Test Control Panel to Rational® Integration Tester Scenario Editor. For information about creating and running scenarios in Rational® Test Control Panel, refer to Scenarios.

In the Scenario Editor, you can configure a scenario. To open the Scenario Editor, double-click the scenario on the Config tab of the Test Suite window. Alternatively, right-click the scenario on the Config tab of the Test Suite window, and click Edit Scenario on the menu.