Welcome
Getting Started
This guide provides an overview and describes the tasks to get you started with HCL DevOps Test Integrations and APIs (Test Integrations and APIs).
DevOps Test Virtualization Control Panel overview
HCL DevOps Test Virtualization (Test Virtualization) stubs that are designed in HCL DevOps Test Integrations and APIs (Test Integrations and APIs) are published to HCL DevOps Test Virtualization Control Panel (Test Virtualization Control Panel), which holds them in a repository.
Sharing and managing stubs
If the purpose of a particular Test Integrations and APIs project is to develop and test a component that requires virtualization (stubbing), that project must own that stub but it can be shared across other projects that need to use it.

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 Integrations and APIs (Test Integrations and APIs). 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 Integrations and APIs (Test Integrations and APIs) 2024.03 (11.0.1).
Getting Started
This guide provides an overview and describes the tasks to get you started with HCL DevOps Test Integrations and APIs (Test Integrations and APIs).
- Overview of DevOps Test Integrations and APIs
  You can use HCL DevOps Test Integrations and APIs (Test Integrations and APIs) to create, modify, and run service tests.
- Testing methodology
  By following four basic guidelines, you can incorporate HCL DevOps Test Integrations and APIs (Test Integrations and APIs) into your testing methodology. These guidelines drive efficient and expedient integration testing, and they can be applied to your testing process and infrastructure requirements.
- Service-oriented architecture (SOA) testing
  A SOA consists of business processes that are implemented by linking individual services. The linking can be done programmatically or with tools based on Business Process Execution Language (BPEL). SOA testing can be challenging because there is no GUI; the focus is on testing interfaces and services.
- Getting started with testing in DevOps Test Integrations and APIs
  You can start using HCL DevOps Test Integrations and APIs (Test Integrations and APIs) by completing the preliminary tasks such as creating and running a test, creating and running a stub, recording an HTTP proxy, and running a stub in a Docker container.
- DevOps Test Virtualization Control Panel overview
  HCL DevOps Test Virtualization (Test Virtualization) stubs that are designed in HCL DevOps Test Integrations and APIs (Test Integrations and APIs) are published to HCL DevOps Test Virtualization Control Panel (Test Virtualization Control Panel), which holds them in a repository.
  - Domains and environments
    You can use domains to group and manage test assets. Within a domain, you can have one or more environments, which can use to group test variables and test tags.
  - Deploying stubs
    For the stub to access the correct data source, you must publish each stub to the correct domain and environment that is the one that contains that stubs data source.
  - Publishing several versions of the same stub
    During testing, you might discover that you require several versions of a stub and you might not want to override the previous version.
  - Running stubs
    When several versions of a stub are deployed, it is possible to run all versions of them in the same environment.
  - Sharing and managing stubs
    If the purpose of a particular Test Integrations and APIs project is to develop and test a component that requires virtualization (stubbing), that project must own that stub but it can be shared across other projects that need to use it.
- DevOps Test Integrations and APIs accessibility features
  Users who have a physical disability, such as limited vision, can review the available accessibility features to use HCL DevOps Test Integrations and APIs (Test Integrations and APIs).
Administrator Guide
This guide describes how to install HCL DevOps Test Integrations and APIs (Test Integrations and APIs). After you install the software, you can perform administration tasks such as configuration and integration of the product. This guide is intended for administrators.
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.
Test Manager Guide
This guide describes the tasks that you can perform for tracking the quality of the application. This guide is intended for Test Managers.
Troubleshooting
While working with HCL DevOps Test Integrations and APIs (Test Integrations and APIs), you might encounter some problems that you can easily troubleshoot.
Reference Guide
This guide provides the topics to help the API tester use the product by using the user interface, commands or scripts. This guide is intended for API testers.
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.

Sharing and managing stubs

If the purpose of a particular Test Integrations and APIs project is to develop and test a component that requires virtualization (stubbing), that project must own that stub but it can be shared across other projects that need to use it.

A change in stub function can be carried out by the stub owner, unless there are specific reasons why another the project might need a different version. In that case, other projects can develop other versions of the stub. However, coordination between projects will be mandatory and the reason for a different stub version must be logged and traceable.

It is likely that other projects that are joining the system under test will want to interact with a stub owned by another project because they might be sharing components that are unavailable.

Consider the following points:

If the same stub version is used, there might be no problem so long as the performance of the stub is satisfactory.
If a different version of the stub is required, the different stub version can be created and maintained by the project that requires it.
Note: Change endpoint parameters, such as queue names, to ensure that they do not clash with the original stub.