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.
Tester Guide - Integration Testing
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.
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.
Managing test results
Use IBM® Rational® Test Control Panel to manage test results with command-line APIs.
Renaming Suites or tests in the results database by using the command line
You can use the command line to verify and rename all Suites and tests that have either moved to a different location or are renamed and which are stored in a results database.

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.
- Tester Guide - Integration Testing
  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.
  - Integration Testing
    You can use find information about the tasks that you can perform for testing various domains, technologies, or applications.
  - 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
      You can use the supported Ant tasks that is supplied with Rational® Test Control Panel to create, update, or manage the environment, scenarios, and stubs.
    - 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.
    - Managing test results
      Use IBM® Rational® Test Control Panel to manage test results with command-line APIs.
      - Deleting all results by using the command line
        You can delete all results and project data that is stored in the results database and you no longer require the stored results by using the Rational® Integration Tester command line.
      - Deleting historical test results data by using the command line
        You can delete historical test suite results or the stub results and specify the results that you want to retain by using the Rational® Integration Tester command line.
      - Renaming Suites or tests in the results database by using the command line
        You can use the command line to verify and rename all Suites and tests that have either moved to a different location or are renamed and which are stored in a results database.
    - 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.
- 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.

Renaming Suites or tests in the results database by using the command line

You can use the command line to verify and rename all Suites and tests that have either moved to a different location or are renamed and which are stored in a results database.

The syntax to rename all Suites and tests that are stored in a results database is as follows:

IntegrationTesterCmd --project <project_name> sync-results-tree

For example, if the project is c:\MyProjects\testproject1. The command to rename all Suites and tests that are stored in a results database is as follows:

IntegrationTesterCmd --project c:\MyProjects\testproject1 sync-results-tree

Before you run the command to rename the Suites or tests in a results database, you can use the following options to get the details about the Suites or tests that are in the results database and the Suites or tests were either renamed or moved.

IntegrationTesterCmd --project <project_name> --dryRun --verbose sync-results-tree

For example, the command can be as: IntegrationTesterCmd --project c:\MyProjects\testproject1 --dryRun --verbose sync-results-tree

The result of this command lists all of the project resources that are in the results database, along with information about whether they were moved, renamed, or there was no change.

The following table lists the options that you can use with the IntegrationTesterCmd command.

Table 1. List of available options
Options	Description
--project/-p	Path to project file (optional). Used to limit the deletion to test suite results to a specific project. If not specified then `databaseUrl`, `dbuser`, and `password` are the required options.
--dryRun	Displays the information about project resources in the results database configured in the project, whether they were moved, renamed, or there was no change. This command option only lists the details and does not perform any renaming action.
--verbose	Provides additional information when used.