Welcome
HCL OneTest™ API reference
HCL OneTest™ API is a scripting-free environment for developing tests for service-oriented architecture (SOA) messaging and business process integration projects. Tests can be built by recording existing system behaviors or from requirements, by entering the data to send and the data that is expected in return.
Scripting within tests and stubs
You can write scripts in HCL OneTest™ API by using the HCL OneTest API legacy scripting language, ECMAScript (such as JavaScript™), or a third-party scripting language that you install.
ECMAScript (Javascript) scripting language
Converting legacy functions to ECMAScript
ECMAScript follows its own string parsing rules. Hence, while converting legacy functions to ECMAScript, ensure that you adhere to the following guidelines:

Release Notes
This document contains information about What's new, installation, known issues, known limitations, and contact information of HCL support.
API Tester Guide (New user)
Typically, a user with the API tester role is responsible for certain tasks including creating and running tests and virtual services to determine the quality of the API layer of the system. This guide lists all such topics to help the new API tester get started with the product.
Administrator Guide
Typically, a user with the administrator role is responsible for certain tasks including installation, configuration, and integration of the product. This guide lists all such topics.
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.
Test Manager Guide
Typically, a user with the Test Manager role is responsible for certain tasks that includes tracking the quality of the application. This guide lists all such topics.
Troubleshooting: HCL OneTest™ API
While working with HCL OneTest™ API, you might encounter some problems that you can easily troubleshoot.
HCL OneTest™ API reference
HCL OneTest™ API is a scripting-free environment for developing tests for service-oriented architecture (SOA) messaging and business process integration projects. Tests can be built by recording existing system behaviors or from requirements, by entering the data to send and the data that is expected in return.
- 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 this 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.
- 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 write scripts in HCL OneTest™ API by using the HCL OneTest API legacy scripting language, ECMAScript (such as JavaScript™), or a third-party scripting language that you install.
  - Legacy scripting language
    Scripts written in the legacy scripting language represent a single or composite expression from the built-in and custom functions. By using a Function action within a test, you can enter an expression that refers to a specific function by name (built-in or custom). These expressions can be used in the Function or Decision action types, and within individual message fields to provide dynamic content. More complex expressions can refer to several functions by using a nested bracket syntax, which is familiar to programmers, for example: eq(5,abs(5.2)), which is the same as eq(5,5.2) and evaluates to "false."
  - ECMAScript (Javascript) scripting language
    - Converting legacy functions to ECMAScript
      ECMAScript follows its own string parsing rules. Hence, while converting legacy functions to ECMAScript, ensure that you adhere to the following guidelines:
    - Using ECMAScript with JSON objects
      You might want to configure a guard condition for a JSON message. You can use a Function action and ECMAScript, which supports JSON objects.
    - ECMAScript editor syntax highlighter
      When editing function actions that use ECMAScript (JavaScript™) the syntax is checked and invalid code is highlighted.
  - Built-in functions
    All the built-in functions can be called from HCL OneTest™ API scripting languages (ECMAScript and Legacy). The built-in functions are available in the legacy scripting language and most of them are available in the ECMAScript scripting language as well. The only exception is the null() function, because the scripts use the null keyword.
  - Adding other scripting languages
    In addition to ECMAScript, you can customize HCL OneTest™ API to use other scripting languages. The language must provide a .jar archive that implements the Java™ Scripting API and that you can embed in the product.
- 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.
Security Considerations
You can take certain actions to ensure that your installation is secure, customize your security settings, and set up user access controls.
Notices
This document provides information about copyright, trademarks, terms and conditions for product documentation.

Converting legacy functions to ECMAScript

ECMAScript follows its own string parsing rules. Hence, while converting legacy functions to ECMAScript, ensure that you adhere to the following guidelines:

All strings must be enclosed in quotation marks, with appropriate escape sequences:
- Quotation marks within the value of the string must be preceded by a backslash (\")
- Backslashes must be preceded by another backslash (\\)
  Example legacy function:
```
setTag(testFileName, C:\myfile.txt)
```
  After conversion to ECMAScript:
```
setTag("testFileName", "C:\\myfile.txt")
```
  or
```
testFileName = "C:\\myfile.txt"
```
Replace the null() function with the null keyword.
Example legacy function:
```
setTag(testTag, null())
```
After conversion to ECMAScript:
```
setTag("testTag", null)
```
or
```
testTag = null
```
Although the setTag() function is still valid in ECMAScript, you can assign values directly instead:
Example legacy function:
```
setTag(testTag, newValue)
```
After conversion to ECMAScript:
```
testTag = "newValue"
```
or
```
tags["testTag"] = "newValue"
```
Note: A direct reference to a tag named id must be qualified with tags. In ECMAScript you can reference a tag with:
```
tags["myTagName"]
tags.get("myTagName")
tags.myTagName
myTagName
```
When the tag name is id, tags.id resolves correctly during execution.
Similarly, you can replace the legacy add() function with an operator:
Example legacy function:
```
add(%%testTag%%, 1)
```
After conversion to ECMAScript:
```
testTag + 1
```
ECMAScript functions do not recognize double percent signs (%%). Therefore, when you write a function, do not enclose the tags in double percent signs as you would in a legacy function. HCL OneTest™ API tags are automatically exposed as ECMAScript local variables.
- In most cases, you can treat the tag name as a local variable:
  Example legacy function:
```
resetTags(%%variable%%)
```
  After conversion to ECMAScript:
```
resetTags(variable)
```
  Example legacy function:
```
xpath(%%xml%%, %%xpathString%%)
```
  After conversion to ECMAScript:
```
xpath(xml, xpathString)
```
- Tag names that include symbols or reserved words can cause problems; in those cases use the tags["tagname"] style of notation.
  Same example, after conversion to ECMAScript:
```
xpath(tags["xml"], tags["xpathString"])
```