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.
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.
Stub creation by using the Recording Studio
Use the Recording Studio to create a message-based stub if you have access to a live system from which you can record events.
Managing recorded events data
HCL DevOps Test Virtualization Control Panel (Test Virtualization Control Panel) can be used to manage and share recorded events data exported from HCL DevOps Test Integrations and APIs (Test Integrations and APIs).

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.
    - Message-based stubs overview
      A message-based stub is essentially an HCL DevOps Test Integrations and APIs (Test Integrations and APIs) resource that listens for incoming messages on a particular transport. A stub can reply to specific messages or message-types, matched according to incoming filters, by using message case actions.
    - Creating an empty stub
      You can create an empty stub. You can add content later by using the stub editor.
    - Creating a stub by using MEP
      You can use the message exchange pattern (MEP) properties for an operation, which define binding and timeout details, to create a stub.
    - Creating a stub populated with data
      You can create a stub based on the structure of the schema that is defined for the operation and the have the response payload populated with data.
    - Stubs with multiple operations
      You can create a single stub to manage multiple operations as a unit. Such a stub is required if you need to share state across several operations.
    - Stub creation by using the Recording Studio
      Use the Recording Studio to create a message-based stub if you have access to a live system from which you can record events.
      - Creating basic stubs
        A basic stub, also called a hardcoded stub, is a stub that always returns the same response. You can create a basic stub from recorded events by using the Recorded Events wizard from the Recording Studio perspective.
      - Creating parameterized stubs
        A parameterized stub, also called a data-driven stub, is one that uses a data source such as a spreadsheet. You can create a data-driven stub from recorded events.
      - Creating data model-driven stubs
        Data models provide an alternative way to store data for a stub. This method creates stubs from recorded events, and such stubs can reuse the data across multiple operations.
      - Creating a stub that manages multiple operations using recorded messages
        Create a stub with multiple operations by using the Recording Studio perspective. Such a stub is required if you need to share state across several operations.
      - Reply-sequenced stubs
        In the Recording Studio perspective, you can create a stub that can send different replies to a particular request, depending on the state of the tag data store for the stub.
      - Managing recorded events data
        HCL DevOps Test Virtualization Control Panel (Test Virtualization Control Panel) can be used to manage and share recorded events data exported from HCL DevOps Test Integrations and APIs (Test Integrations and APIs).
        Searching recorded events data
        You can search recorded events data stored in HCL DevOps Test Virtualization Control Panel (Test Virtualization Control Panel). After retrieving the required data, you can view, edit, and delete it.
  - 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.
  - 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).

Managing recorded events data

HCL DevOps Test Virtualization Control Panel (Test Virtualization Control Panel) can be used to manage and share recorded events data exported from HCL DevOps Test Integrations and APIs (Test Integrations and APIs).

The Library page of Test Virtualization Control Panel enables you to search, view, edit, delete, and thus manage recorded events data captured in the Recording Studio perspective and exported from Test Integrations and APIs. You can also use the Library page to share your recorded events data with other users of the same instance of Test Virtualization Control Panel.

You can import recorded events data from Test Virtualization Control Panel into your Test Integrations and APIs project and use it to create tests and stubs. Other users in the same instance of Test Virtualization Control Panel can also edit and delete your recorded events data, and import the data into their Test Integrations and APIs projects.

Note: There are limitations with importing recorded events into a project that is different from the project from which they were exported. .

Note: You cannot import or export recorded events data from within Test Virtualization Control Panel. Test Integrations and APIs is the only application that can be used to import and export recorded events.