Welcome
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.
Messages
Test Integrations and APIs 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.
Message bodies
The message body is constructed below the message header in publishers and subscribers.
Creating message bodies with non-schema transports
When you are using transports without a defined message schema (for example, TIBCO Rendezvous), the body of the message must be created manually.

Release Notes
This document includes information about the new features introduced, features deprecated or removed, defects fixed, and known issues identified in this version of HCL DevOps Test Integrations and APIs (Test Integrations and APIs). You can also find the installation and upgrade instructions along with the contact information of HCL Customer Support.
System requirements
This document includes information about hardware and software requirements for HCL DevOps Test Integrations and APIs (Test Integrations and APIs) 2024.03 (11.0.1).
Getting Started
This guide provides an overview and describes the tasks to get you started with HCL DevOps Test Integrations and APIs (Test Integrations and APIs).
Administrator Guide
This guide describes how to install HCL DevOps Test Integrations and APIs (Test Integrations and APIs). After you install the software, you can perform administration tasks such as configuration and integration of the product. This guide is intended for administrators.
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
This guide describes the tasks that you can perform for tracking the quality of the application. This guide is intended for Test Managers.
Troubleshooting
While working with HCL DevOps Test Integrations and APIs (Test Integrations and APIs), you might encounter some problems that you can easily troubleshoot.
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.
- DevOps Test Integrations and APIs overview
  This section provides an overview of HCL DevOps Test Integrations and APIs (Test Integrations and APIs), including information about projects and files, the Test Integrations and APIs 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 Test Integrations and APIs, 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 Test Integrations and APIs. 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
  Test Integrations and APIs 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.
  - Selecting transports and formatters
    The first step in building a message is to select a transport and formatter, available at the top of the message Config tab.
  - Message headers
    Message headers contain metadata about the message itself (for example, sender and destination details, message properties, message type). Headers for different transports contain different types of information.
  - Message bodies
    The message body is constructed below the message header in publishers and subscribers.
    - Publisher/subscriber views
      The structure of a message is defined when you are using the publish/subscribe actions. In each action type, different views of the message can be selected. On selecting a view, information relating to the storage and validation of the message is displayed.
    - Importing and exporting messages
      You can export the current message or import a previously saved or exported message. The import and export icons at the top of all message editors.
    - Quick tags
      A fast way to insert tags into fields is to use quick tags.
    - Defining the validation rules (comparison ignores)
      Rules can be added to one or more message fields to define default actions to apply when you are processing similar fields.
    - Creating message bodies with non-schema transports
      When you are using transports without a defined message schema (for example, TIBCO Rendezvous), the body of the message must be created manually.
    - Example: Publishing simple message bodies
      A simple message body has a specific structure.
    - Example: Creating simple message bodies for subscription
      In this example, you create a message structure with the more powerful features of the field editor, namely, the ability to validate the structure of a message when it is received and the ability to capture field values and save them to tags. Validation is a key aspect of deciding whether a test passes or fails.
    - Formatting a JSON message
      If the received message contains a JSON string, you can apply the JSON format so that the contents of the message is easy to understand.
    - Converting a flat XML to structured XML
      A powerful feature of the HCL DevOps Test Integrations and APIs (Test Integrations and APIs) message editor is the ability to enter XML in String type fields and then edit the XML in a structured way.
    - Editing XML message structures
      Editing XML is similar to editing normal message structures, but with a few enhancements. The following options in the element menu apply specifically to editing XML.
  - Using repeating and optional elements
    You can use Test Integrations and APIs to create repeating elements within a message from a test data set or to read all values from repeating elements in a received message.
  - Formatting a message with MIME, S/MIME, DIME, and multipart content
    When you are working with messages that can contain multiple parts, you must format the message as a Multipurpose Internet Mail Extensions (MIME) message. You can also apply a MIME or a Direct Internet Message Encapsulation (DIME) schema to the message. You can apply the secure MIME (S/MIME) standard to encrypt or digitally sign outbound messages.
  - Adding attachments to a message
    Attachments can be added to parts of a message by right-clicking the wanted node and selecting Add Attachment from the menu.
  - Configuring the XML message properties for test actions
    By using message properties in Test Integrations and APIs, you can configure how message content is treated in test actions (for example, Publish, Subscribe).
  - Creating messages and applying them to tests
    You can create a message that contains requirements and drag that message onto an action in a test. After you create a message, you can build it by specifying the transports and formatters.
  - Messaging transports, formatters, and dynamic formatters
    Test Integrations and APIs uses a decoupled, plug-in architecture to provide maximum flexibility in regards to the messaging transport software in use by a system under test. A formatter translates messages from the native transport format (for example, TIBCO Rendezvous) to the internal format understood by Test Integrations and APIs, known as A3 (Accelerated Adaptor Architecture).
  - The Field Editor
    Use the Field Editor to specify that a message field (data attribute) be populated by using or fulfilling certain criteria. Open the editor by double-clicking a field or element name within a message or a stub, by or right-clicking the field and selecting Contents > Edit.
  - Troubleshooting: Messages
    You can use a workaround to a problem that you might encounter when you work with message fields.
- Schemas
  Test Integrations and APIs 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
  Test Integrations and APIs 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 DevOps Test Integrations and APIs (Test Integrations and APIs) 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 Test Integrations and APIs that include the Test Integrations and APIs legacy scripting language, ECMAScript (such as JavaScript™), Chai, or any third-party scripting language that you install.
- External tools
  Test Integrations and APIs is primarily GUI-based, but you can also run or view tests, suites, and stubs outside of the Test Integrations and APIs.
- 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 Test Integrations and APIs, 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 DevOps Test Integrations and APIs (Test Integrations and APIs), 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.

Creating message bodies with non-schema transports

When you are using transports without a defined message schema (for example, TIBCO Rendezvous), the body of the message must be created manually.

Right-click the message root to view the menu and begin constructing the message body. Using these commands, arbitrarily complex tree structures can be built. The menu for all objects in the message-tree is essentially the same.

Contents provides access to field and XML actions, quickly creating a Tag action, and opening up the Field Editor for the selected part of the message. Use the field editor for enabling the type and value of the field to be edited, and field validation and tag storage. See The Field Editor.
Schema invokes the schema wizard for creating schema-based messages.
Repeating allows creation of repeating elements within a message from a test data set.
Rule Cache provides options for creating rules or managing existing rules.
Type allows the field type to be reselected.
Root allows selection of the root of the schema if there is more than one root.
Properties displays the properties associated with message in a separate dialog.
Previewdisplays the message either in Bytes mode or in String mode.
- In Bytes mode, the message will be shown in Hex (hexadecimal) format by default; you can also select Text and an encoding format, as appropriate.
- In String mode, the message will be shown in a collapsed form.
Note: The Preview option was previously present in the Field Properties dialog.
Add Child (if applicable) adds a child to the end of the message tree.
Move Up and Move Down move the current element up or down, relative to the other elements, if possible.
Delete deletes the selected object.
Cut, Copy, and Paste work like they do in other applications (that is, cutting, copying, or pasting the selected item to/from the clipboard).
Expand All and Collapse All expands or collapses the selected message node.
Note: When you are expanding all nodes in large messages, Test Integrations and APIs processes the message for up to 5 seconds. After that time, all nodes that could be expanded will be expanded. If necessary, you can expand again to continue expanding any collapsed nodes.
Add Attachment lets users add a file attachment to the selected message node.