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.
Scenarios
In HCL® Quality Server, you can create scenarios, which are collections of configured stubs that can be started and stopped together.
Starting a scenario
After creating a scenario in HCL® Quality Server, you can start it.

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.
        Creating a scenario
        You can create a scenario in HCL® Quality Server to control a collection of configured stubs.
        Starting a scenario
        After creating a scenario in HCL® Quality Server, you can start it.
        Modifying a scenario
        You can modify a scenario that is currently running from the Environments Dashboard in HCL® Quality Server. You can add stubs to a scenario, modify the stub configuration, delete a stub from a scenario, modify the stub behavior during start of the scenario, rename a scenario, or delete a scenario from the Environments Dashboard.
        Stopping a scenario
        You can stop scenarios that are starting or running in HCL® Quality Server.
      - Stopping stubs
        You can use HCL® Quality Server, HCL OneTest™ API, or Docker to stop the stubs.
    - 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.

Starting a scenario

After creating a scenario in HCL® Quality Server, you can start it.

Before you begin

Optional: To prevent other users from interrupting your testing, lock the environment that you are using. If you lock the currently selected environment, the locked status message is displayed on the Environments Dashboard.

Procedure

Log in to HCL® Quality Server.
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.
Note: If you are using 8.5.1.1 or later and domain-level security is enabled, you can use only the domains to which you were granted access.
Identify the scenario you want to start.

Note:
You can identify a scenario on the Environments Dashboard from the Start Scenario icon () that is present for a scenario, while the stub can be identified from the Start stub icon () it has.
For the scenario you want to start, click the Start icon () on the Environments Dashboard.

Note: All the stubs that were running when you created the scenario can be seen included under the new scenario.

Results

The scenario starts. The status of the scenario changes from STOPPED to STARTING or RUNNING.

In 8.5.1 or later:

If a scenario tries to start more instances of a stub than there are available agents (for example, four stub instances on three agents), HCL® Quality Server displays a message about insufficient agents and problems. If you choose to ignore these problems and continue, the number of stub instances started will equal the number of available agents, which will be less than the number of stub instances saved in the scenario.
If you have multiple subs in a scenario and each stub has multiple instances that are configured to run on multiple agents (for example, two stubs, each with three instances, and configured to run on three agents), HCL® Quality Server will start the scenario and not display any messages if the required number of agents is available. This is because separate stubs in a scenario are treated independently of each other and because scaling out applies to multiple stub instances and not to multiple stubs.