Welcome
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.
Tester Guide - Service Virtualization
This guide describes the tasks that you can perform for using virtual services or stubs to simulate parts of an environment if the real services are not yet available or because they are difficult or expensive to use. This guide is intended for API Testers.
Publishing and running stubs
You can publish stubs that are created in HCL DevOps Test Integrations and APIs (Test Integrations and APIs) to HCL DevOps Test Virtualization Control Panel (Test Virtualization Control Panel), Dockerfile and build context, Kubernetes, or Istio, if the stub is based on a supported transport.
Behaviors for stubs
You can create a simple behavior called "echo" that will expose one function and one event for use by a HCL DevOps Test Virtualization (Test Virtualization) stub.
Introduction to behaviors
Behaviors are reusable behavioral units that can expose utility or business logic for use within HCL DevOps Test Virtualization (Test Virtualization).

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).
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.
- Tester Guide - Integrations and API Testing
  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. This guide is intended for Integrations and API testers.
- Tester Guide - Service Virtualization
  This guide describes the tasks that you can perform for using virtual services or stubs to simulate parts of an environment if the real services are not yet available or because they are difficult or expensive to use. This guide is intended for API Testers.
  - DevOps Test Virtualization overview
    HCL DevOps Test Virtualization (Test Virtualization) is software that is used for creating, maintaining, publishing, and running message-based stubs and database stubs.
  - Virtualizing HTTP
    You can simulate an HTTP connection with a virtual service, also known as a stub.
  - Virtualizing HTTPS
    You can simulate an HTTPS connection with a virtual service, also known as a stub.
  - Virtualizing TCP
    You can simulate a TCP connection with a virtual service, also known as a stub.
  - Virtualizing a REST API without recording or synchronization
    You can virtualize REST APIs by using the Recording Studio, or by synchronizing WADL, Swagger, or RAML documents. When none of these options is available, you can still manually virtualize REST APIs that use path parameters.
  - Creating message-based stubs
    In HCL DevOps Test Integrations and APIs (Test Integrations and APIs), there are several methods that you can use to create a message-based stub.
  - Modifying message-based stubs
    You can use either the Test Editor or the Stub Editor to create, modify, and enhance any legacy or new stubs created by HCL DevOps Test Integrations and APIs (Test Integrations and APIs).
  - Creating and modifying database stubs
    You can create and modify database stubs in HCL DevOps Test Integrations and APIs (Test Integrations and APIs).
  - Configuring stubs to connect to DevOps Test Virtualization Control Panel and the HTTP proxy
    A stub running on its own may not be sufficient in some cases, because it might have dependencies on services such as HCL DevOps Test Virtualization Control Panel (Test Virtualization Control Panel) or the HTTP proxy. If the stub is running on the public cloud and the services are running in the enterprise, you must configure the stub to connect to these services.
  - Publishing and running stubs
    You can publish stubs that are created in HCL DevOps Test Integrations and APIs (Test Integrations and APIs) to HCL DevOps Test Virtualization Control Panel (Test Virtualization Control Panel), Dockerfile and build context, Kubernetes, or Istio, if the stub is based on a supported transport.
    - Publishing stubs
      You can publish a stub to HCL DevOps Test Virtualization Control Panel (Test Virtualization Control Panel), Dockerfile and build context, Kubernetes, or Istio with Kubernetes by using the HCL DevOps Test Integrations and APIs (Test Integrations and APIs) Publish Stubs wizard.
    - Running stubs
      Several methods are available to start and stop the stubs. You can also modify and control stubs while they are running.
    - Modifying running stubs
      If you are using HCL DevOps Test Integrations and APIs (Test Integrations and APIs) to run a stub, you can modify the stub while it is running.
    - Controlling running stubs
      You can control stubs that are running in a number of ways.
    - Behaviors for stubs
      You can create a simple behavior called "echo" that will expose one function and one event for use by a HCL DevOps Test Virtualization (Test Virtualization) stub.
      - Introduction to behaviors
        Behaviors are reusable behavioral units that can expose utility or business logic for use within HCL DevOps Test Virtualization (Test Virtualization).
      - Creating behaviors for stubs
        You can create behaviors to expose utility or business logic for use within HCL DevOps Test Virtualization (Test Virtualization).
      - Interface definitions
        You can define interfaces for the echo behavior.
  - Viewing results in DevOps Test Virtualization Control Panel
    You can use HCL DevOps Test Virtualization Control Panel (Test Virtualization Control Panel) to display the results of tests that you run in both HCL DevOps Test Integrations and APIs (Test Integrations and APIs) and Test Virtualization Control Panel.
  - Viewing usage statistics of virtual services in DevOps Test Virtualization Control Panel
    Test Virtualization Control Panel collects and stores usage metric data. The metric data might include the number and types of actions that are used, the features that are used in the workbench, details about Operating System or languages set while running, and so forth. You cannot view the metric data on the Test Virtualization Control Panel user interface, but it is available from the underlying implementation. Storage is either managed by H2 or optionally Apache Cassandra.
  - Viewing reports in DevOps Test Hub
    All the project stakeholders can view test reports for multiple testing products from the Results page on HCL DevOps Test Hub (Test Hub). You can access the Results page from a web browser. Therefore, there is no need to install the desktop client.
  - Troubleshooting: DevOps Test Virtualization
    You can use workarounds to common problems that you might encounter when you use HCL DevOps Test Virtualization (Test Virtualization).
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.

Introduction to behaviors

Behaviors are reusable behavioral units that can expose utility or business logic for use within HCL DevOps Test Virtualization (Test Virtualization).

They can be combined to build rich virtual servers (stubs) with minimal development effort.

A behavior interacts with a stub in two ways:

It provides methods that can be used within script actions in the business logic of a stub. This enables the stub to control the behavior at run time.
It can raise events to the stub, passing information that tells the stub that the behavior needs to interact in some way, such as sending a message.

Behaviors are discovered by Test Virtualization at run time for use in stubs by means of an Eclipse extension: com.greenhat.tester.api.behaviour and they have the following four primary elements:

The factoryClass is a Java™ class whose package is exported by the behavior-contributing plug-in that implements the com.greenhat.tester.api.behaviour.BehaviourFactory interface. The implementation of the class creates and returns an implementation of the behavior and typically will configure and add listeners to it.
The behaviourInterface is a Java™ interface that is an extension of the com.greenhat.tester.api.behaviour.LifecycleAwareBehaviour interface whose package is exported by the behavior-contributing plug-in, which exposes the functions of the behavior.
The callbackInterface is a Java™ interface whose package is exported by the behavior-contributing plug-in and exposes the events exposed as call-backs by the behavior.
The implementation of the behavior is custom code that is typically instantiated and configured by the factoryClass, which implements the behaviourInterface and makes call-backs on the callbackInterface.