Home
Reference Guide
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.
Database resources, connections, and bindings
HCL OneTest™ API can interact with any database that supports connectivity through the JDBC specification. These interactions can be used to extract or update data where necessary, and test data sets can be taken directly from database table content.
Binding a logical resource to a physical database
The logical database resource is selected in HCL OneTest™ API tests. Therefore, it must be bound to an actual (physical) database before any real testing can occur.

Reference Guide
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.
- HCL OneTest™ API overview
  This section provides an overview of HCL OneTest™ API, including information about projects and files, the HCL OneTest API user interface, environments, and project settings and preferences.
- Architecture School
  Use the Architecture School perspective to build a system under test by using the logical, physical, and synchronization views. You can also use this perspective to manage the schemas available in your project.
- Recording Studio
  With HCL OneTest™ API, you can record events (messages or database interactions) sent to and from the system under test. Use Recording Studio to control what parts of the system should be recorded. These parts could be specific parts of the system infrastructure or specific services using that infrastructure. You can then use the recorded events as a source of tests and other interactions with the system. In Recording Studio, you can record the traffic over a number of different transports.
- Test Factory
  The Test Factory perspective is one of the main areas in HCL OneTest™ API. You can create all the tests and the required artifacts/data to support them.
- Test Lab
  You use the Test Lab to execute test assets, repair tests, and open test assets for editing directly from this perspective. You can execute all of the tests, test suites, and stubs that are created in Test Factory.
- Results Gallery
  You use the Results Gallery perspective to view an execution summary and detailed coverage, and error reports for executed test suites and for test cases that were executed within a suite or as part of a test cycle.
- Messages
  HCL OneTest™ API can publish and subscribe to messages as part of a test. A message normally consists of two parts: a header and a body. The header usually adheres to a predefined logical construction, while the structure of the body can be more arbitrary.
- Schemas
  HCL OneTest™ API can handle many types of content. For the product to be able to interpret the variety of content types, it must associate a content format description, or schema with the content.
- Database resources, connections, and bindings
  HCL OneTest™ API can interact with any database that supports connectivity through the JDBC specification. These interactions can be used to extract or update data where necessary, and test data sets can be taken directly from database table content.
  - Adding a logical resource
    To provide access to a database, you need to add a logical resource to the HCL OneTest™ API project.
  - Adding a physical resource
    The physical database represents an actual database that you want to test. Connection details and stored procedure settings are configured on the physical resource.
  - Binding a logical resource to a physical database
    The logical database resource is selected in HCL OneTest™ API tests. Therefore, it must be bound to an actual (physical) database before any real testing can occur.
  - Configuring the physical database resource
    After you create a physical database, you can configure the details of the physical database.
  - Adding an SQL Command action to a test
    The SQL Command action runs an SQL command (insert, update, or delete rows) against a selected database. As you add this action, you can validate or store into a tag the number of rows that are affected.
  - Adding an SQL Query action to a test
    The SQL Query action queries the selected database to verify that its contents match the selected values. As you add this action, you can validate or store the query results.
  - Adding a Stored Procedure action to a test
    The Stored Procedure action runs a stored procedure against the selected database. As you add this action, you can view the code of the stored procedure, specify input values, specify expected return values, or tag return values.
- Identity stores and SSL
  An identity store can group a collection of one or more certificates that can be used in HCL OneTest™ API to validate and authenticate connections that use SSL. After you create an identity store, you can use it to enable SSL communications in various messaging transports.
- Scripting within tests and stubs
  You can use scripts in HCL OneTest™ API that include the HCL OneTest API legacy scripting language, ECMAScript (such as JavaScript™), Chai, or any third-party scripting language that you install.
- External tools
  HCL OneTest™ API is primarily GUI-based, but you can also run or view tests, suites, and stubs outside of the HCL OneTest API.
- Test actions
  Actions are the building blocks of a test. A test consists of a series of steps and each step is an action. Actions can be defined for tests and stubs.
- Formatting and parsing date-time patterns
  For some fields in HCL OneTest™ API, you can define patterns for date-time formatting. Pattern letters are repeated, as their number determines the exact presentation of the date-time information that they represent.
- The Add Numbers service
  The Add Numbers service, included with HCL OneTest™ API, provides a simple way to generate messages that you can observe with topology discovery or capture in Recording Studio.

Binding a logical resource to a physical database

The logical database resource is selected in HCL OneTest™ API tests. Therefore, it must be bound to an actual (physical) database before any real testing can occur.

About this task

This binding between logical and physical resources is configured in an environment, which can be done in one of two ways.

Setting binding in Architecture School
Setting binding in environment editor

Setting binding in Architecture School

Procedure

Right-click the logical database in the Architecture School Logical View and select the Set Binding in option, choosing the wanted environment and physical database resource.

Setting binding in environment editor

Procedure

Click the environment icon to open the environment editor.
From the list of environments on the left, select the environment in which you want to configure the binding.
In the row that contains the logical database, select the physical resource.