Home
Rational® Performance Tester
Test Execution Specialist Guide
This guide describes tasks that you can perform on schedules, test execution with custom code, and Extending Rational® Performance Tester to support other protocols. This guide is intended for testers or test execution specialists.
Extending Rational® Performance Tester to support other protocols
The Rational® Performance Tester Extensibility Software Development Kit (SDK) enables you to create extensions to support testing new protocols without modifying the core product code. You can create an extension that provides functionality for testing other protocols in addition to the HTTP protocol support that is standard in Rational Performance Tester.
Extending the test editor
The performance testing software provides application programming interface (API) classes for extending the test and performance tools platform (TPTP) to write new editors and protocol extensions.
Common editor framework
Extend performance test editing in the common editor framework. It contains the classes to extend for specific behaviors that will be used by the extended editor implementations.

Rational® Performance Tester
- Release Notes
  This document contains information about what's new, installation instructions, known issues in IBM® Rational® Performance Tester, and contact information of IBM Customer Support.
- System Requirements
  This document includes information about hardware and software requirements for IBM® Rational® Performance Tester.
- Getting Started
  This guide provides an overview and describes the task flows to get you started with Rational® Performance Tester. This guide is intended for new users.
- Tutorials
  This section contains the tutorials which explains the main features of Rational® Performance Tester.
- Samples
  This section describes about the sample project which can be used with Rational® Performance Tester to test the functionality of an application.
- Administrator Guide
  This guide describes how to install Rational® Performance Tester. After you install the product, you can perform administration tasks such as license configuration and integration with other products. This guide is intended for administrators.
- Test Author Guide
  This guide describes how to create test scripts in Rational® Performance Tester and enhances tests by applying different test elements such as dataset, variables, and verification points. This guide is intended for testers.
- Test Execution Specialist Guide
  This guide describes tasks that you can perform on schedules, test execution with custom code, and Extending Rational® Performance Tester to support other protocols. This guide is intended for testers or test execution specialists.
  - Running schedules with performance testing
    After you have added the user groups, tests, and other items to a schedule, and you are satisfied that it represents a realistic workload, you run the schedule.
  - Extending test execution with custom code
    You can extend how you run your tests by writing custom Java™ code and calling the code from the test. You can also specify that results from the tests that are affected by your custom code be included in reports.
  - Extending Rational® Performance Tester to support other protocols
    The Rational® Performance Tester Extensibility Software Development Kit (SDK) enables you to create extensions to support testing new protocols without modifying the core product code. You can create an extension that provides functionality for testing other protocols in addition to the HTTP protocol support that is standard in Rational Performance Tester.
    - Protocol extension structure
      Before organizing your extension, note the restrictions and guidelines provided in this topic.
    - Extending the test recorder
      To generate a test, the data exchanged by an application and another entity such as a server must be recorded. The recorded data is then processed to generate a test.
    - Extending the test generation framework
      Test generation consists of processing the recorded data and producing a test.
    - Contributing annotations
      An annotation is an action that a user performs during a recording session. Annotations are used to document or structure the test generated from the recording.
    - Extending the load test behavior model
      The load test behavior model (LTBM) is a model of the behavior of a performance test in Rational® Performance Tester.
    - Extending data correlation
      Data correlation is the process of extracting data that is returned from a server, and then sending it back to the server in a subsequent request.
    - Extending the test editor
      The performance testing software provides application programming interface (API) classes for extending the test and performance tools platform (TPTP) to write new editors and protocol extensions.
      - Migrating test editor extensibility
        Changes in the performance testing editor base framework package are provided in this release to support more standardized ways of handling model element attributes.
      - Test editor structure
        The editor in Rational® Performance Tester is built of several layers; the common framework, the editor and the protocol layer.
      - Common editor framework
        Extend performance test editing in the common editor framework. It contains the classes to extend for specific behaviors that will be used by the extended editor implementations.
        The modelObjectDescriptor extension point
        The modelObjectDescriptor extension point combines and enhances the deprecated contentProvider, labelProvider, layoutProvider, and actionHandler extension points.
        The testOptions extension point
        The testOptions extension point is used to contribute user interface elements for displaying options for a protocol in the Details area of the root element in the tree, Performance Test or schedule, in this context, is used to refer to VU Schedule and Rate Schedule. Each contribution is displayed in a separate tab in a Tab folder.
      - Contributing actions to the menu
        You can use extensions to extend the menu, change navigation, and perform data correlation.
      - Editor layer extension points
        The editor layer enables you to write protocol extensions. During the initialization process, a number of extension points are checked for extensions that define different aspects of the test editor.
      - API classes
    - Contributing error handlers
      An error handler is associated with an error condition. Error handlers specify the action to take when a specified error condition occurs. Error handlers are provided for conditions such as verification-point failures, connection failures, server timeouts, and data-correlation problems. You can add new types of errors and error handlers.
    - Extending the schedule component
      When you extend the schedule component in performance testing, another plug-in can contribute options to a schedule. Those options can be set up to persist in the schedule model, and a corresponding user interface can be displayed for editing the new options.
    - Extending code generation
      The code generation subsystem maps Load Test Behavior Model (LTBM) elements to objects of the code generation element model (IModelElement), which in turn are mapped to objects of its ILanguageElement class. As a result, a language element tree is created that contains all equivalent elements of the behavior model test element tree and at the same time determines the structure of code to be generated.
    - Extending the run-time environment
      The run-time environment defines the plug-ins on which all other plug-ins depend. The run-time environment is responsible for defining a structure for plug-ins and the implementation detail behind them.
    - Extending the test log viewer
      After running a test, the test results are saved in a test log. Use the Test Log viewer to check the results for specific events, such as the script start and end, loop, invocation, message, or verdict.
    - Extending evaluation results
      Reports are a specification of how performance test data should be extracted from the statistical model and presented to the user.
- Test Manager Guide
  This guide describes how to keep track of the performance of the application by evaluating the test results. This guide is intended for test managers.
- Troubleshooting Guide
  This guide describes how to analyze and resolve some of the common problems that you might encounter while you work with Rational® Performance Tester.
- Reference Guide
  This guide describes, additional topics to gain more knowledge about Rational® Performance Tester.
- All Guides (PDFs)
  You can find the link to view or download the content of the release notes, system requirements, and persona guides of Rational® Performance Tester as a PDF file.
- 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 the product documentation.

Common editor framework

Extend performance test editing in the common editor framework. It contains the classes to extend for specific behaviors that will be used by the extended editor implementations.

Because performance testing editors are extensions loaded and initialized by the TPTP platform through the org.eclipse.hyades.ui.editorExtensions extension point, one of the common editor framework functions is to provide hooks and application programming interfaces (APIs) for concrete editor implementations to communicate with TPTP. The common editor framework defines the classes to be used by higher editor implementations. One of the most widely used classes is the TestEditor class, which is extended by the com.ibm.rational.test.lt.testeditor.main.LoadTestEditor plug-in.

The layoutProvider, labelProvider, contentProvider and actionHandler extension points have been deprecated and are superseded by the modelObjectDescriptor extension point that combines and enhances them. The following table lists the active extension points that you can use to extend the common editor framework:


Extension point	Description
`modelObjectDescriptor`	Specifies the type of the object, the test editor, and the general name and icon for the object.
`testOptions`	Used to contribute user interface (UI) elements for displaying the protocol options in the Details area of the root element in the tree, Performance Test or Schedule.
`editorAddonEnabler`	Used to write contributions to existing user interface (UI). It can have enabled and displayed state. Works with the `AddonReader` class.
`searchTypeProvider`	Contributes a search category to the performance testing Search window. The category consists of object type and, optionally, search parameters.
`searchTypeOptionsContibutor`	Contributes extra search parameters to some other search type category.
`preferencePageContributor`	Provides a way to create extensible preference pages as well as to contribute UI to other preference pages. For preference pages, use the Eclipse extension point and extend the class `com.ibm.rational.common.test.editor.framework.kernel.EditorPreferenecePage`. For page contributions, use this extension point and extend the `com.ibm.rational.common.test.editor.framework.kernel.TestPreferenceContributor` class.