Home
Test Author Guide
This guide describes how to create test scripts in HCL OneTest™ Performance and enhances tests by applying different test elements such as dataset, variables, and verification points. This guide is intended for testers.
Sending service requests with the generic service client
The generic service client enables you to send requests to services for which you do not have a convenient client and to view the responses returned by the service.
Creating transport protocol configurations
Read these topics to configure various transport protocols.
Creating a JMS transport configuration
You can create an JMS transport configuration that describes the transport settings for a service request that uses the Java™ Message Service (JMS) protocol, including JBoss and IBM® WebSphere® JMS. Transport and security settings can be associated with any service request.

Test Author Guide
This guide describes how to create test scripts in HCL OneTest™ Performance and enhances tests by applying different test elements such as dataset, variables, and verification points. This guide is intended for testers.
- Creating tests
  To create a test, you record representative interactions with an application.
- Editing tests
  After you record a test, you can edit it to include datasets (to provide variable data rather than the data that you recorded), verification points (to confirm that the test runs as expected), and data correlation (to ensure that returned data is appropriate for the corresponding request). You can also add protocol-specific elements to a test. When you edit a test, the modified items appear in italic type. The italic type changes to regular type after you save the test.
- Compound tests
  You can create compound tests to help you organize smaller tests into scenarios that can then be run end-to-end. You can combine tests from different extensions to achieve end-to-end flow.
- Simulating services with stubs
  Service stubs enable you to simulate the behavior of an actual service for a wide variety testing or integration purposes.
- Sending service requests with the generic service client
  The generic service client enables you to send requests to services for which you do not have a convenient client and to view the responses returned by the service.
  - Creating transport protocol configurations
    Read these topics to configure various transport protocols.
    - Creating an HTTP transport configuration
      You can create an HTTP transport configuration that describes the transport settings for a service request. Transport and security settings can be associated with any service request.
    - Configuring the workbench for NTLMv2 authentication
      NTLMv2 authentication requires access to a third-party library. To record and execute a test that contains NTLMv2 authentication, you must download the library and place it at the right location.
    - Creating a JMS transport configuration
      You can create an JMS transport configuration that describes the transport settings for a service request that uses the Java™ Message Service (JMS) protocol, including JBoss and IBM® WebSphere® JMS. Transport and security settings can be associated with any service request.
    - Creating a WebSphere® MQ protocol configuration
      When you want to send requests to a service that uses WebSphere MQ transport protocol, you can create a protocol configuration to describe the transport settings for a service request.
    - Creating a WebSphere® Java MQ transport configuration
      You can create a transport configuration that describes the transport settings for a service request that uses the IBM® WebSphere® Java MQ protocol. Transport and security settings can be associated with any service request.
    - Creating Microsoft™ .NET transport configurations
      You can manually create a Microsoft™ .NET transport configuration to describe the transport settings for service requests that use the Windows™ Communication Foundation (WCF) protocol.
    - Creating SSL configurations
      You can create a Secure Sockets Layer (SSL) configuration that describes the settings for a service request that uses SSL certification mechanisms. SSL configurations can be associated with any service request that uses the HTTP or IBM® WebSphere® MQ transport protocols.
  - Sending service requests with WSDL files
    You can send requests to services based on SOAP, Java Messaging Service (JMS), WebSphere® MQ, and Microsoft™ .NET that use a Web Service Description Language (WSDL) file to specify the contents of the service request.
  - Sending HTTP endpoint requests
    You can send requests to services that use an HTTP endpoint.
  - Sending a JMS endpoint request
    You can send requests to services that use a Java™ Messaging Service (JMS) endpoint.
  - Sending a WebSphere® MQ endpoint request
    You can invoke calls to services that use a WebSphere® MQ endpoint.
  - Sending OData endpoint batch requests
    To test services that use OData protocol, you can send requests in a batch. The request contains HTTP operations such as GET, POST, and PUT to manage data in the service.
  - Sending WebSphere Java MQ endpoint requests
    You can send requests to services that use a WebSphere Java MQ endpoint.
  - Testing all operations in a WSDL file
    You can use the generic service client to rapidly send requests to a service using all the operations in a Web Services Description Language (WSDL) file. The calls are generated with default values based on the type of data.
  - Viewing message content
    The Raw Transaction Data view displays the raw XML, text, or binary content of any service request or response that is selected in the generic service client.
  - Synchronizing a remote WSDL file
    For web services that make their Web Services Description Language (WSDL) file available from a URL, you might have to ensure that the WSDL that you work with is always up to date. By synchronizing the WSDL, you ensure that the local copy of the WSDL in your workspace is regularly synchronized with the remote WSDL.
  - Synchronizing a local WSDL file with GSC
    If you edit a local WSDL source file, the Generic Service Client (GSC) should display the changes in the UI. You must keep the GSC up-to-date with the WSDL changes to ensure that you test the latest service request.
  - Adding static XML headers to a service request
    You can add static XML headers to service requests to ensure compliance with WS-Addressing, WS-ReliableMessaging, and WS-Coordination specifications as well as other predefined standards.
  - Opening file attachments
    When a service sends a file attachment with the response, you must import it as a resource to open the attachment.
- Emulating workloads
  You emulate a workload by creating a schedule and adding user groups/rate runner groups, tests, and other elements to it.

Creating a JMS transport configuration

You can create an JMS transport configuration that describes the transport settings for a service request that uses the Java™ Message Service (JMS) protocol, including JBoss and IBM® WebSphere® JMS. Transport and security settings can be associated with any service request.

Before you begin

If you are using SOAP security, ensure that you have configured the environment with the correct libraries and configuration files.

Procedure

Click the Generic service client toolbar button to open the generic service client and click the Transport tab.
This opens the Transport Configurations page.
On the Transport Configurations page, click one of the following buttons:
- Create a basic JMS configuration () to create a new generic JMS transport configuration.
- Create a JBoss JMS configuration () to create a JMS configuration preconfigured for JBoss.
- Create a WebSphere JMS configuration () to create a JMS configuration preconfigured for WebSphere® JMS.
Type a Name for the new transport configuration and select whether the service is a queue or a topic destination.
Type the address of the JMS end point.
Select Use temporary object to provide the address of the reception point to the service as a temporary object. If you disable this setting, you must manually specify the reception point address.
If the service requires authentication, select Basic Authentication and type the user name and password to access the service.
If the service requires a custom Java™ Naming and Directory Interface (JNDI) adapter, you can provide your own Java™ class that extends the Apache Axis class. In this case, select Custom Adapter and specify the name of the custom Java™ class. See Extending test execution with custom code for more information about custom code.
Specify whether the message type is Text or Binary.
If necessary, click Add or Edit to specify the Context factory properties or Connector properties required to access the service.
Click OK to create the new configuration.

What to do next

Once created, you can use your new configuration with any service request that uses the JMS transport protocol. You can use the Configurations list in the generic service client to edit existing configurations or to create duplicate configurations.