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.
API 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 OneTest™ API.
Modifying database stubs
You can modify database stubs in HCL OneTest™ API.
Editing database stub wizard
You can use the Edit Database Stub wizard to edit the contents of the currently selected database stub.
The database stub edit spreadsheet
You can edit the contents of a database stub by using the Edit Database Stub wizard. A spreadsheet editor is opened in which you can modify the stub. The editor contains information about how the spreadsheet is started and the spreadsheet format.

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.
- API Tester Reference
  This guide provides the topics to help the API tester use the product by using the user interface, commands or scripts. This guide is intended for API testers.
- API 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.
  - Task flow: Working with the HCL Quality Server Environments dashboard
    You can use the HCL Quality Server Environments dashboard to perform various tasks such as starting, stopping stubs and scenarios, and modifying stub configurations after you have published stubs to HCL Quality Server. You can also lock the environment that contain the published 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.
    - 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.
    - 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 OneTest™ API can be non-persistent or persistent.
    - JDBC proxy
      The HCL OneTest™ API JDBC proxy package is provided with HCL Quality Server. 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 OneTest™ API 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 OneTest™ API.
    - Synonyms
      A synonym is an alias or alternate name for a table, view, sequence, or other schema object. HCL OneTest™ API 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 OneTest™ API to create a database stub while SQL events are being recorded from a database.
    - Modifying database stubs
      You can modify database stubs in HCL OneTest™ API.
      - Example: Using pass-through in database stubs
      - The editing options toolbar
        With the editing options toolbar, you can work with the database stubs.
      - Editing database stub wizard
        You can use the Edit Database Stub wizard to edit the contents of the currently selected database stub.
        Editing using SQL queries
        You can edit using SQL Queries in the Edit Database Stub wizard.
        Editing tables
        You can edit tables using the Edit Database Stub wizard.
        The database stub edit spreadsheet
        You can edit the contents of a database stub by using the Edit Database Stub wizard. A spreadsheet editor is opened in which you can modify the stub. The editor contains information about how the spreadsheet is started and the spreadsheet format.
      - Refresh wizard
        With the Refresh wizard, you can import additional data from a live database into the currently selected stub.
      - Add wizard
        You can use the Add wizard to add more queries, tables, stored procedures, or sequences to the currently selected database stub.
      - External edit wizard
        You can use the External Edit wizard to use any database management systems tools (to which you have access) to edit the contents of the currently selected database stub.
  - 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.
  - 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. For more information about the H2 database and its management, see sections A. Server Configuration and D. Deleting Data.
  - 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.

The database stub edit spreadsheet

You can edit the contents of a database stub by using the Edit Database Stub wizard. A spreadsheet editor is opened in which you can modify the stub. The editor contains information about how the spreadsheet is started and the spreadsheet format.

Spreadsheet editor

A temporary .xls file is created and the system default spreadsheet editor is started.

Note: This default can be overridden by explicitly associating a .xls editor under Applications Preferences (See Changing preferences and, specifically, Applications preferences).

Spreadsheet format

The spreadsheet can take two forms, which are based on the type of database information it represents:

Database table spreadsheet format
Database stored procedure spreadsheet format

Database table spreadsheet format

Each page represents a single table. The title of the page is the table name. The first row contains the column names and subsequent rows contain the respective values:

Any value that you select in the spreadsheet can be edited.
A new column can be added to the table by entering a new column name in the header cell and the database-type to be used for the column, and then by entering values for each row.
Note: The type name must be in parentheses. For example, NEW_COL (VARCHAR(20)).
An existing column's name or type cannot be modified.

Note: If you select to edit the contents of multiple tables for simultaneous editing, each table is on a separate page.

Database stored procedure spreadsheet format

The spreadsheet can contain the following pages:

Inbound parameters: The page contains the names of the inbound parameters on the first row. You can specify your own values on the second row.
Outbound parameters: The page contains the names of the outbound parameters and the result code on the first row. You can specify your own values on the second row (result code is 0 by default)
Result Set 1, Result Set 2, and so on: The pages are present if the stored procedure returns result sets. The first row contains the column names and subsequent rows contain the respective values.

A new result set can be added by adding a spreadsheet page, whose title is of the form Result Set <n>, where <n> is the new result set number.