Management of virtualized services

You can find information about the tasks that you can perform on and manage the virtualized services that run on HCL DevOps Test Hub (Test Hub). You can start or stop the virtual services that are available to Test Hub. You can view the routing rules and usage statistics of virtualized services, agents, or intercepts that are connected to Test Hub.

You can create stubs or virtual services in HCL DevOps Test Integrations and APIs (Test Integrations and APIs). You must commit the virtual service resources to a remote Git repository, and then add the Git repository to your project on Test Hub if you used Test Integrations and APIs to create virtual service resources.

You can start a running instance of the virtual services from Test Hub to run on the following locations:
  • A registered API agent.
  • The default Kubernetes cluster of Test Hub.
  • A remote Kubernetes cluster.

You can run all virtual services on registered API agents except the virtual services that use CICS transport, DB2/Z transport, or Istio.

The default Kubernetes cluster or a remote Kubernetes cluster supports running of the following types of virtual services:
  • Virtual services that utilize the WebSphere® MQ transport.
  • Virtual services that utilize the HTTP transport.
Restriction: You cannot run virtual services on a remote Docker host.
If running a virtual service in a Kubernetes cluster, the following are the considerations that decide the selection of a container:
  • Before a container is selected to run a virtual service, it is checked for a previous failure to start a virtual service or for a low heap size, and other conditions. If the container was not found suitable, then it is not selected for running the virtual service.
  • Multiple virtual services can be run in the same container if the following conditions are satisfied:
    • Subsequent virtual services are started by the same project member.
    • All virtual services are created and contained in the same Test Integrations and APIs project.
    • The requests to run the virtual services refer to the same version, meaning that the git commit IDs on which they are based are the same. If you use the UI, this means that the Version field in the Execute virtual service dialog are the same.
    • The settings that you configure in the Advanced settings for the virtual services are the same.
    • The datasets selected for an override are the same, if datasets are used.

Working with virtual services

You can perform the following tasks on virtual services on Test Hub: