Welcome
Test Execution Specialist Guide
This guide describes tasks that you can perform on schedules, test execution with custom code, and Extending HCL DevOps Test Performance (Test Performance) to support other protocols. This guide is intended for testers or test execution specialists.
Extending DevOps Test Performance to support other protocols
The HCL DevOps Test Performance (Test 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 Test Performance.
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.
Code generation
The com.ibm.rational.test.lt.codegen.core.extLibraryDependency extension point has been modified.

Release Notes
This document includes information about the new features introduced, features deprecated or removed, defects fixed, and known issues identified in this version of HCL DevOps Test Performance (Test Performance). You can also find the installation and upgrade instructions along with the contact information of HCL Customer Support.
System Requirements
This document includes information about hardware and software requirements for HCL DevOps Test Performance (Test Performance) 2024.03 (11.0.1).
Getting Started
This guide provides an overview and describes the task flows to get you started with HCL DevOps Test Performance (Test Performance). This guide is intended for new users.
Tutorials
This section contains the tutorials which explains the main features of HCL DevOps Test Performance (Test Performance).
Samples
This section describes about the sample project which can be used with HCL DevOps Test Performance (Test Performance) to test the functionality of an application.
Administrator Guide
This guide describes how to install HCL DevOps Test Performance (Test Performance). 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 HCL DevOps Test Performance (Test Performance) 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 HCL DevOps Test Performance (Test 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 DevOps Test Performance to support other protocols
  The HCL DevOps Test Performance (Test 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 Test 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.
  - Extending the load test behavior model
    The load test behavior model (LTBM) is a model of the behavior of a performance test in HCL DevOps Test Performance (Test 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.
    - Code generation
      The com.ibm.rational.test.lt.codegen.core.extLibraryDependency extension point has been modified.
    - Extension points for code generation
      During the initialization process a number of extension points are checked for existence of extensions that define different aspects of the code generation behavior.
    - Generating test code
      During the initialization phase of a code generation request, an object extending the LTTestExtensionPreferences class is created by calling all plug-ins implementing the com.ibm.rational.test.lt.codegen.core.codegenProtocolExtension extension point through their supportFeatures() method.
    - Creating the script class
      After all model language elements are processed and the code language elements created, the code for the script class is generated.
    - Code generation templates
      The code generation subsystem uses declaration templates and creation templates.
    - New protocol extensions
      This section describes the implementation of the code generation subsystem extension for the socket protocol as an example of using code generation extensibility features.
    - Public APIs of codegen.core
      The public APIs contain the public interfaces and classes used to extend the code generation core subsystem.
  - 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 HCL DevOps Test Performance (Test Performance).
Reference Guide
This guide describes, additional topics to gain more knowledge about HCL DevOps Test Performance (Test Performance).
All Guides (PDFs)
You can find the link to view or download the content of the release notes, system requirements, and persona guides of HCL DevOps Test Performance (Test Performance) 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.

Code generation

The com.ibm.rational.test.lt.codegen.core.extLibraryDependency extension point has been modified.

The com.ibm.rational.test.lt.codegen.core.extLibraryDependency extension point has been modified in the following ways:

supportedFeature has been added with attribute featureName, which is the feature ID of this protocol extension as defined by extending the com.ibm.rational.test.lt.licensing.feature extension point. If this element is specified, and the test being generated does not contain this feature, the existence of external libraries will not be enforced. This will prevent the developer from requiring that libraries are invalid for various OS platforms. If the element is not defined, external libraries are enforced as before, so no existing code is broken. Essentially these external libraries will not be enforced for tests that do not contain this feature.
optionalExtLibraryLocation has been added with attribute pathname (the same as the one for the existing extLibraryLocation element). Libraries defined by this element are deployed when present. If they are not present, however, no warning will be raised. An optional external library might have the supported feature defined, so if the test does not contain the feature, the optional library, even if it exists, will not be deployed.
optionalExtLibraryLocation and extLibraryLocation have a new attribute, RelativetoExternalFiles. Set this attribute to true if you are providing a library that is in the external_files directory and to false if you are providing a library that is relative to your plug-in.