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 OneTest™ API to HCL® Quality Server, 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.
Stopping stubs
You can use HCL® Quality Server, HCL OneTest™ API, or Docker to stop the stubs.
Stopping stubs by using the Integration tester method
You can stop stubs using the HCL OneTest™ API method.

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 - 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 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.
  - HCL OneTest™ Virtualization overview
    HCL OneTest™ 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 OneTest™ API, 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 OneTest™ API.
  - Creating and modifying database stubs
    You can create and modify database stubs in HCL OneTest™ API.
  - Configuring stubs to connect to HCL® Quality Server 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® Quality Server 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 OneTest™ API to HCL® Quality Server, 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® Quality Server, Dockerfile and build context, Kubernetes, or Istio with Kubernetes by using the HCL OneTest™ API 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® Quality Server, HCL OneTest™ API, or Docker can be used to start stubs.
      - Scenarios
        In HCL® Quality Server, you can create scenarios, which are collections of configured stubs that can be started and stopped together.
      - Stopping stubs
        You can use HCL® Quality Server, HCL OneTest™ API, or Docker to stop the stubs.
        Stopping stubs by using the Server method
        When you want to stop stubs that are running on HCL® Quality Server, you can stop individual stubs or stop multiple stubs from the Environments Dashboard or Infrastructure Dashboard.
        Stopping stubs by using the Integration tester method
        You can stop stubs using the HCL OneTest™ API method.
        Stopping stubs that are running in a Docker container
        Use the docker stop command to stop stubs that you published to a Docker container.
        Stopping stubs that are running in Istio or Kubernetes
        When you no longer require the stub that is running in an Istio or a Kubernetes deployment, you can delete the virtual service of the stub or delete the complete deployment of the stub.
    - Modifying running stubs
      If you are using HCL OneTest™ API 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 OneTest™ Virtualization stub.
  - Viewing results in HCL® Quality Server
    You can use HCL® Quality Server to display the results of tests that you run in both HCL OneTest™ API and HCL Quality Server.
  - Viewing usage statistics of virtual services in HCL® Quality Server
    HCL® Quality Server 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 HCL Quality Server user interface, but it is available from the underlying implementation. Storage is either managed by H2 or optionally Apache Cassandra.
  - Viewing reports in HCL OneTest™ Server
    All the project stakeholders can view test reports for multiple testing products from the Results page on HCL OneTest™ Server. You can access the Results page from a web browser. Therefore, there is no need to install the desktop client.
  - Troubleshooting: HCL OneTest™ Virtualization
    You can use workarounds to common problems that you might encounter when you use HCL OneTest™ Virtualization.

Stopping stubs by using the HCL OneTest™ API method

You can stop stubs using the HCL OneTest™ API method.

To stop a stub, do the following steps:

In HCL OneTest™ API Test Lab perspective, find the stub to stop.
Select the stub and click Stop on the Task Monitor windows toolbar.
Alternatively, select the stub and click Stop on the Task Monitor toolbar.

Stopping a message-based stub causes the following to happen:

If traffic was being routed automatically routed to the stub by means of a HCL OneTest™ API Proxy, the proxy will be configured to resume sending messages to the live system.

Stopping a database stub causes the following to happen:

HCL OneTest™ API instructs each proxy to return to the state it was in before the stub was started.
The simulation schema is cleared.

Note: Stopping a persistent stub updates the stub with a fresh snapshot of data. A non-persistent stub is not updated and, if started again, it will revert to its original state. If there is no connection to the database, exceptions are recorded in a log. In HCL OneTest™ Virtualization, stubs cannot be persistent.