Home
Test Execution Specialist Guide
This guide describes tasks that you can perform on schedules, test execution with custom code, and Extending HCL OneTest™ Performance to support other protocols. This guide is intended for testers or test execution specialists.
Extending HCL OneTest™ Performance to support other protocols
The HCL OneTest™ Performance 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 HCL OneTest Performance.
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.
Contributing new actions to the annotation toolbar
Typically, you produce an annotation by adding an action to the annotation toolbar. This action is represented as a toolbar button.

Test Execution Specialist Guide
This guide describes tasks that you can perform on schedules, test execution with custom code, and Extending HCL OneTest™ Performance 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 HCL OneTest™ Performance to support other protocols
  The HCL OneTest™ Performance 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 HCL OneTest Performance.
  - 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.
    - Defining a new annotation type
      Each annotation type has its own semantics and supports a set of properties.
    - Contributing new actions to the annotation toolbar
      Typically, you produce an annotation by adding an action to the annotation toolbar. This action is represented as a toolbar button.
    - Generating a test-model element from a new annotation type
      After annotations have been inserted into a recording session, the annotations must be processed by a test generator to translate them into a test-model element. To process annotations with a test generator, define a dedicated test generator or modify an existing test generator that you have developed.
    - Advanced annotation concepts
      In some rare cases, annotations can be produced by recorders or clients.
  - Extending the load test behavior model
    The load test behavior model (LTBM) is a model of the behavior of a performance test in HCL OneTest™ Performance.
  - 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.
  - 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.

Contributing new actions to the annotation toolbar

Typically, you produce an annotation by adding an action to the annotation toolbar. This action is represented as a toolbar button.

To contribute a new action to the annotation toolbar, complete these procedures:

Declare a new annotation action in the plugin.xml file by using the com.ibm.rational.test.lt.recorder.ui.annotationContribution extension point and the annotationAction element.
Assign a unique ID to the annotation action.
Decide whether this action is visible by default or not. Actions that are visible by default are available in all recording sessions unless made unavailable by a client or recorder. Actions that are not visible by default are available only if a recorder or client requires the action.
Define an implementation class for this action. The implementation class must extend the com.ibm.rational.test.lt.recorder.ui.actions.AbstractAnnotationAction abstract class.

Consider these facts about AbstractAnnotationAction implementations:

This class extends the JFace Action class.
In the constructor, set the name, tooltip text, and image descriptor of the action.
Implement the run() method. This method can interact with the user. For example, this method can prompt the user for a text field. If there is any interaction with the user, the time in milliseconds spent interacting with the user must be measured.
To create an annotation, create an instance of the com.ibm.rational.test.lt.recorder.core.annotations.RecorderAnnotation class, and then pass the annotation type as an argument. Set the annotation properties using the setter methods provided in this class.
After the annotation has been built, forward the annotation by sending an AnnotationMessage message to the annotation recorder. This is typically a call of this form: annotationRecorder.sendMessage(new AnnotationMessage(annotation, interactionTime));