Home
Rational® Performance Test Server
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.
Managing scenarios
Use HCL Quality Server to manage scenarios with command-line, Ant, and REST APIs.

Rational® Performance Test Server
- 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 __PTS_RR_NAME__.
- Getting Started
  This guide provides an overview and describes the tasks to get you started with IBM® Rational® Performance Test Server.
- 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.
  - 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 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 HCL OneTest™ API functionality by using custom functions
      You can add more calculations and operations to tests by using the HCL OneTest™ API custom function class. HCL OneTest API 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
        HCL OneTest™ API command-line client is available in HCL OneTest API 8.0.1 or later.
      - Ant tasks
        Support for the environment, scenario and stub Ant tasks is supplied with HCL Quality Server.
      - REST services
        Representational state transfer (REST) is a simple stateless architecture that generally runs over HTTP. When used in conjunction with HCL Quality Server, HTTP methods (such as GET and POST) are mapped to actions on domains, environments, scenarios, stubs and other resource types.
      - Running tests
        Use HCL OneTest™ API to run tests with command-line and Ant APIs.
      - Managing test results
        Use HCL Quality Server to manage test results with command-line APIs.
      - Managing domains
        You can create, list, update, and delete domains with the HCL Quality Server REST API.
      - Managing environments
        Locking a HCL Quality Server environment prevents other users from changing the state of that environment, for example, starting or stopping stubs.
      - Managing scenarios
        Use HCL Quality Server to manage scenarios with command-line, Ant, and REST APIs.
        Start a scenario by using the command line
        You can start a scenario by using the HCL OneTest™ API command line. This option is useful in situations where Ant is not available.
        Stop a scenario by using the command line
        You can stop a scenario by using the HCL OneTest™ API command line, optionally waiting for the scenario to stop before exiting. This option is useful in situations where Ant is not available.
        Start a scenario by using an Ant task
        You can start a scenario by using the HCL Quality Server Ant tasks.
        Stop a scenario by using an Ant task
        You can stop a scenario by using the HCL Quality Server Ant tasks.
        REST services
        Representational state transfer (REST) is a simple stateless architecture that generally runs over HTTP. When used in conjunction with HCL Quality Server, HTTP methods (such as GET and POST) are mapped to actions on domains, environments, scenarios, stubs and other resource types.
      - Managing stubs
        You can manage stubs by using the command-line, Ant, and REST APIs.
- 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.

Managing scenarios

Use HCL Quality Server to manage scenarios with command-line, Ant, and REST APIs.

Scenario selection

Use HCL Quality Server API to manage scenarios.

When selecting scenarios, the domain, environment, name and owner options must uniquely identify the scenario to start.

If there is only one scenario in an environment, only domain and environment are required.
If a user has only one scenario in an environment, domain, environment, and owner can be specified to uniquely identify that scenario. Otherwise domain, environment, and name are required to uniquely identify the scenario.
If the command is being used in an automated script, the name must always be used even if, at the time of writing the script, one of the preceding alternatives would be sufficient. This is because using the name creates resilience against future changes in the environment's list of scenarios.
It is possible to specify domain, environment, name, and owner, which would have the effect of uniquely identifying the scenario and verifying that it was created by a specific user.