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.
Controlling running stubs
You can control stubs that are running in a number of ways.
Locking and unlocking environments
Locking a HCL DevOps Test Virtualization Control Panel (Test Virtualization Control Panel) environment prevents other users from starting or stopping stubs in that environment.
Unlocking an environment
You can unlock an environment in HCL DevOps Test Virtualization Control Panel (Test Virtualization Control Panel).

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 Virtualization (Test Virtualization). 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 Test Virtualization.
Getting Started
This guide provides an overview and describes the tasks to get you started with Test Virtualization.
Administrator Guide
Typically, a user with the administrator role is responsible for certain tasks including installation, configuration, and integration of the product. This guide lists all such topics.
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.
      - Locking and unlocking environments
        Locking a HCL DevOps Test Virtualization Control Panel (Test Virtualization Control Panel) environment prevents other users from starting or stopping stubs in that environment.
        Locking an environment in HCL DevOps Test Virtualization Control Panel (Test Virtualization Control Panel)
        When you lock an environment, you can continue to use the environment but other users cannot make any changes to it.
        Unlocking an environment
        You can unlock an environment in HCL DevOps Test Virtualization Control Panel (Test Virtualization Control Panel).
      - Viewing broken stub messages
        On HCL DevOps Test Virtualization Control Panel (Test Virtualization Control Panel) Environments Dashboard page, if a stub fails to start (irrespective of from where the stub is started) and displays a Broken state, placing your mouse pointer over the stub displays a message about the possible cause for the Broken state. See the Agent logs for more details of the cause.
      - Viewing stub logs
        HCL DevOps Test Virtualization Control Panel (Test Virtualization Control Panel) enables HCL DevOps Test Virtualization (Test Virtualization) users to view the console output of stubs that ran in the selected domain and environment.
      - Query Docker container logs
        You can use the docker logs commands to query Docker container logs.
      - Debugging message-based stubs
        Use the Message Differences window or options available within the stub console display to debug message-based stubs.
    - 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).
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.
Security Considerations for DevOps Test Virtualization
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.

Unlocking an environment

You can unlock an environment in HCL DevOps Test Virtualization Control Panel (Test Virtualization Control Panel).

Procedure

Log into Test Virtualization Control Panel.
Note: If you are not an administrator user, you must use the user name that you used to lock the environment.
The application window is displayed.
Click the Environments icon or navigation link.

The Environments Dashboard is displayed.
You can change the domain and environment you want to view by clicking the domain/environment link, and from the domain/environment selection dialog displayed, select the domain, and then select the environment.

The Environments Dashboard is displayed for the selected environment and domain.
If you are not the user who locked the environment, you can request for unlocking the environment or wait until the locked time to pass. The expected end time is shown in the message when you place the cursor over the Lock icon or in the Unlock Environment window.
Click the Lock icon ().
In the Unlock Environment window, enter your reason for unlocking in the Reason for environment Unlock field and then, click REQUEST UNLOCK.
- If you are the user who locked the environment, the Unlock Request? dialog is displayed and you can either REJECT or APPROVE the unlock request.
- If you are the user requesting the unlocking of the environment, the unlock request is sent to the user who locked the environment and that user can either REJECT or APPROVE the request.

Results

Request for unlocking the selected environment in the selected domain is sent to the user who locked the environment. The unlocked environment is displayed with the unlocked icon ( image of the icon ).

Note: All environment locking and unlocking events, including reasons, are recorded in the Test Virtualization Control Panel Audit log. (For information about this log, refer to Administration of DevOps Test Virtualization Control Panel.)