Home
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.
Running stubs
Several methods are available to start and stop the stubs. You can also modify and control stubs while they are running.
Starting stubs
HCL DevOps Test Virtualization Control Panel (Test Virtualization Control Panel), HCL DevOps Test Integrations and APIs (Test Integrations and APIs), or Docker can be used to start stubs.

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.
      - Starting stubs
        HCL DevOps Test Virtualization Control Panel (Test Virtualization Control Panel), HCL DevOps Test Integrations and APIs (Test Integrations and APIs), or Docker can be used to start stubs.
        Starting stubs by using the DevOps Test Virtualization Control Panel method
        When you want to start stubs that are published to HCL DevOps Test Virtualization Control Panel (Test Virtualization Control Panel), you can do so from the Environments Dashboard. Also, when you cannot use or access HCL DevOps Test Integrations and APIs (Test Integrations and APIs) to control stubs, you can use the Environments Dashboard of Test Virtualization Control Panel to start the stubs.
        Starting stubs by using the DevOps Test Integrations and APIs method
        HCL DevOps Test Integrations and APIs (Test Integrations and APIs) can be used to start stubs, but HCL DevOps Test Virtualization Control Panel (Test Virtualization Control Panel) provides more control over the startup of a stub or a set of stubs.
        Running stubs in a Docker container
        After you publish one or more stubs to a Dockerfile and build context and you built a Docker image from those files, you use the docker run command to run the image in a container.
        Running stubs in Kubernetes
        After you publish one or more stubs to Kubernetes, you must upload the project files to a file server and edit the YAML file to point to the URL of the file server before you can run the stubs.
      - Scenarios
        In HCL DevOps Test Virtualization Control Panel (Test Virtualization Control Panel), you can create scenarios, which are collections of configured stubs that can be started and stopped together.
      - Stopping stubs
        You can use HCL DevOps Test Virtualization Control Panel (Test Virtualization Control Panel), HCL DevOps Test Integrations and APIs (Test Integrations and APIs), or Docker to stop the stubs.
    - 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.
  - 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).

Starting stubs

HCL DevOps Test Virtualization Control Panel (Test Virtualization Control Panel), HCL DevOps Test Integrations and APIs (Test Integrations and APIs), or Docker can be used to start stubs.

There are some limitations on stubs depending on how they are started. The following table describes those limitations.


If a stub is published to Test Virtualization Control Panel and started by Test Virtualization Control Panel...	If a stub is started by Test Integrations and APIs...	If a stub is published to a Dockerfile and build context and an image built and run by Docker...
There are no running time limits on the stub.	It will run for only five minutes unless the associated test scenario requires it to run for a longer period.	There are no running time limits on the stub.
There are no transactions per second (TPS) limits on the stub.	There is a limit of 1 TPS on the stub.	There is a limit of 10 TPS on the stub.

The following topics describe how to use Test Virtualization Control Panel, Test Integrations and APIs, or Docker to start stubs.