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.
Controlling running stubs
You can control stubs that are running in a number of ways.
Locking and unlocking environments
Locking a HCL® Quality Server environment prevents other users from starting or stopping stubs in that environment.
Locking an environment in HCL® Quality Server
When you lock an environment, you can continue to use the environment but other users cannot make any changes to 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.
    - 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.
      - Locking and unlocking environments
        Locking a HCL® Quality Server environment prevents other users from starting or stopping stubs in that environment.
        Locking an environment in HCL® Quality Server
        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® Quality Server.
      - Viewing broken stub messages
        On HCL® Quality Server 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® Quality Server enables HCL OneTest™ 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 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.

Locking an environment in HCL® Quality Server

When you lock an environment, you can continue to use the environment but other users cannot make any changes to it.

Procedure

Log into HCL® Quality Server.
In the application window of 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.
On the Environments Dashboard, click the Lock icon ().

The Lock Environment dialog is displayed. The Domain and Environment fields display the names of the currently selected domain and environment.
Specify the duration length and interval. You must enter the number in the Duration Length field or choose the number by using the scroll button ().
Using the list next to the Duration Interval field, specify whether the duration is measured in minutes, hours, or days.
In the Reason for Lock field, enter a reason for locking the environment. This reason is displayed to all users who view the Environments dashboard and it is logged in the HCL® Quality Server Audit log. For information about this log, see Administration of HCL Quality Server.
Click LOCK.

Results

A closed lock ( image of the icon ) is displayed against the environment to indicate that the environment is now locked.

If you are the user who locked the environment, you can continue to use the environment as usual but other users are prevented from making any changes to it.

If the security functionality of HCL® Quality Server is disabled, user names are not displayed when displaying information about a locked environment.

You can view which of the environments under a domain are locked from the domain/environment selection dialog. Locked environments are displayed with a lock icon ( image of the icon ) next to them.