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 and modifying database stubs
You can create and modify database stubs in HCL DevOps Test Integrations and APIs (Test Integrations and APIs).
Prerequisites for creating database stubs
Before creating any database stubs, you must complete any required software installation tasks and set up the schema that is used for stubbing a physical database.

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.
  - 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).
    - Prerequisites for creating database stubs
      Before creating any database stubs, you must complete any required software installation tasks and set up the schema that is used for stubbing a physical database.
      - Setting up the schema used for stubbing a physical database
        Before you can create database stubs, you must specify in HCL DevOps Test Integrations and APIs (Test Integrations and APIs) which database schema is to be used for the simulation database.
      - Setting up a logical and physical database
        Before you can create database stubs, you must set up a logical and physical database in HCL DevOps Test Integrations and APIs (Test Integrations and APIs).
    - Database stubs overview
      If you want to create a test or suite of tests for an application that uses a database, you run the test (suite) in a repeatable fashion against a known set of database contents. Therefore, you must stub the database to obtain repeatable conditions. Database stubs enable you to execute tests against some parts of a system under test without affecting a live database.
    - Persistence
      Database stubs created in HCL DevOps Test Integrations and APIs (Test Integrations and APIs) can be non-persistent or persistent.
    - JDBC proxy
      The HCL DevOps Test Integrations and APIs (Test Integrations and APIs) JDBC proxy package is provided with HCL DevOps Test Virtualization Control Panel (Test Virtualization Control Panel). You must deploy the package on any stand-alone applications, or application servers that host applications that use JDBC to access any live databases that you want to record or virtualize.
    - Stored procedures
      If you are using HCL DevOps Test Integrations and APIs (Test Integrations and APIs) 8.0.1 or later, you can record and virtualize most stored procedures.
    - Data type support
      You can find information about the data types supported for database management systems in HCL DevOps Test Integrations and APIs (Test Integrations and APIs).
    - Synonyms
      A synonym is an alias or alternate name for a table, view, sequence, or other schema object. HCL DevOps Test Integrations and APIs (Test Integrations and APIs) 8.5.1 or later supports certain synonyms for some supported database management systems.
    - Creating database stubs by using the Recording Studio
      You use the Recording Studio perspective of the HCL DevOps Test Integrations and APIs (Test Integrations and APIs) to create a database stub while SQL events are being recorded from a database.
    - Modifying database stubs
      You can 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).

Prerequisites for creating database stubs

Before creating any database stubs, you must complete any required software installation tasks and set up the schema that is used for stubbing a physical database.

The following topics describe how to complete these prerequisites.

Preparation and planning

For information about installing and configuring the required software, and determining which live databases are to be stubbed and whether there are any database schema or data source requirements, refer to Setting up the JDBC proxy.

Note: The version number of the HCL DevOps Test Virtualization Control Panel (Test Virtualization Control Panel) software that you are using must be the same as the version number of the HCL DevOps Test Integrations and APIs (Test Integrations and APIs) software that you are using. Therefore, if you have upgraded your Test Integrations and APIs installation and you want to record SQL or create database stubs, you must also upgrade your Test Virtualization Control Panel installation and upgrade the JDBC proxy wherever it is deployed.