Welcome
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.
Integration with other products
You can integrate HCL DevOps Test Performance (Test Performance) with certain products to run tests, manage test assets, and create defects.
EGit integration
You can store your test assets in the remote Git repository and use EGit for version control operations. EGit is an Eclipse plugin for the Git version control system.
Pulling the changes from the remote Git repository
You must make your local repository up-to-date by pulling the latest changes in the remote Git repository before you commit and push your updated test assets to the Git repository.

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.
- Installation of DevOps Test Performance
  Installation of the product involves verifying requirements, planning, managing licenses, and configuring web-based help. This section lists all such topics.
- License management
  Licensing for HCL DevOps Test Performance (Test Performance) is administered through HCL Software License & Download portal. This portal is a FlexNet-based web application that helps to manage software entitlements and licenses.
- Product upgrade and migration
  When you want to use the enhanced functionalities of HCL DevOps Test Performance (Test Performance), you must upgrade to the latest version of the product software.
- Configuration of the product
  You must configure HCL DevOps Test Performance (Test Performance) when you want to run SAP tests, collect response time breakdown data, or use the product in the Docker container.
- Integration with other products
  You can integrate HCL DevOps Test Performance (Test Performance) with certain products to run tests, manage test assets, and create defects.
  - Integration plugin compatibility matrix
    You can find information about the versions of the integration plugin that are compatible with HCL DevOps Test Performance (Test Performance).
  - Running tests by using Ant
    When you want to automate repetitive tasks, you can run performance test assets from the command-line interface by using Ant.
  - Integration with Azure DevOps
    When you use Azure DevOps for continuous integration and continuous deployment of your application, you can create tests for your application in HCL DevOps Test Performance (Test Performance) and run those tests in Azure DevOps pipelines.
  - Integration with Apache JMeter
    You can use JMeter tests extension with HCL DevOps Test Performance (Test Performance) to run JMeter tests.
  - EGit integration
    You can store your test assets in the remote Git repository and use EGit for version control operations. EGit is an Eclipse plugin for the Git version control system.
    - Importing test assets from the remote Git repository
      You can import the test assets from the remote Git repository to HCL DevOps Test Performance (Test Performance) and run it to test the performance of the application.
    - Pulling the changes from the remote Git repository
      You must make your local repository up-to-date by pulling the latest changes in the remote Git repository before you commit and push your updated test assets to the Git repository.
    - Publishing test assets to the remote Git repository
      When you create or update any test assets in HCL DevOps Test Performance (Test Performance), you can publish your changes to the remote Git repository. Therefore, when you publish test assets, other members in the project can use your test assets in their test run, if required.
    - Techniques for troubleshooting issues in EGit
      You might encounter issues while working with EGit in HCL DevOps Test Performance (Test Performance). You can find the information about certain issues and how to resolve them.
  - Configuration of test runs as a GitHub Actions Workflow
    You can configure test runs of test resources that are in HCL DevOps Test Performance (Test Performance) in a GitHub Actions Workflow. You can choose to run test resources that are in the project in the GitHub Workflow when you want to run the test resources without opening the Test Performance.
  - Integration with Engineering Test Management
    You can integrate IBM® Engineering Test Management (formerly known as IBM Rational® Quality Manager) with HCL DevOps Test Performance (Test Performance) to initiate test runs from Engineering Test Management.
  - Integration with IBM® Engineering Workflow Management
    You can integrate Engineering Workflow Management (formerly known as Rational® Team Concert™) to create and track defects (bugs) or other work items, as a defect tracking tool in HCL DevOps Test Performance (Test Performance).
  - Integration with HCL DevOps Deploy
    You can integrate HCL DevOps Test Performance (Test Performance) with HCL DevOps Deploy (Deploy) to run performance test assets as a Process from Deploy.
  - Integration with DevOps Test Integrations and APIs
    You can use HCL DevOps Test Integrations and APIs (Test Integrations and APIs) extension to run API tests from Test Performance. You can either import the projects from Test Integrations and APIs or manage them from Test Performance by establishing the connection between the products. You can also create a schedule or compound test to run the tests by using the Agents.
  - Integration with IBM® DevOps Deploy
    You can integrate HCL DevOps Test Performance (Test Performance) with IBM® DevOps Deploy (Deploy) to run performance test assets as a Process from Deploy.
  - Integration of Jaeger with the product
    Jaeger is software for tracing transactions between distributed services. You can use Jaeger to monitor and troubleshoot complex microservices environments.
  - Integration with Jenkins
    You can use the DTPerf-Jenkins-HCL plugin to run tests on a Jenkins server.
  - Testing with Maven
    Starting from 9.2.0, you can use the Maven plug-in that is provided with the testing product to run tests as part of your Maven build. Apache Maven is a software build tool based on the concept of a project object model (POM).
  - Integration with Micro Focus ALM
    You can integrate HCL DevOps Test Performance (Test Performance) with Micro Focus Application Lifecycle Management (ALM) to run performance test assets from Micro Focus ALM.
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.
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.

Pulling the changes from the remote Git repository

You must make your local repository up-to-date by pulling the latest changes in the remote Git repository before you commit and push your updated test assets to the Git repository.

Before you begin

You must have completed the following tasks:

Cloned the remote Git repository. For more information refer to the EGit User Guide documentation.
Ensured that any of your team members have updated the test assets and committed those files to the remote Git repository.

About this task

When you updated any of the test assets in your project, you might see merge conflicts errors while pulling the changes, if other members are also working on the same project.

Procedure

Open Test Performance.
The default perspective is the Performance Test.
Go to Windows > Perspective > Open Perspective > Other.
The Open Perspective window is displayed.
Select the Git option from the list, and then click Open.
The Git perspective view is displayed.
Right-click the remote Git repository from the list, and then select Pull.

Results

You have pulled the new changes from the remote Git repository to your existing local Git repository.

What to do next

You can publish your changes to the remote Git repository. See Publishing test assets to the remote Git repository.