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.
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.
Editing Socket tests
Improve the Socket tests by adding test elements.
Adding elements to a socket test
A socket test provides the flexibility to add close, send, and receive elements to the test.
Adding a socket close
You can manually add a socket close element to a socket API performance test.

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.
  - Editing HTTP tests
    After you record a test, you can edit it to include variable data rather than the data that you recorded and can include verification points to confirm that the test runs as expected. You can also edit the test to include [NB1] transactions, conditional processing, custom code, and standard header or custom header to a request or response.
  - Editing SAP tests
    After you record a test, you can edit it to include variable data (rather than the data that you recorded) and verification points (to confirm that the test runs as expected).
  - Editing Citrix tests
    After you record a test, you can edit it to include variable data (rather than the data that you recorded), verification points (to confirm that the test runs as expected), transactions, conditional processing, and custom code.
  - Editing service tests
    After you record a service test, you can edit the calls and message returns to include variable data (rather than the data that you recorded). You can add verification points (to confirm that the test runs as expected), transactions, conditional processing, and custom code.
  - Editing Socket tests
    Improve the Socket tests by adding test elements.
    - Socket API test editor overview
      You use the test editor to inspect or customize a socket API test that you recorded.
    - Adding elements to a socket test
      A socket test provides the flexibility to add close, send, and receive elements to the test.
      - Adding a socket close
        You can manually add a socket close element to a socket API performance test.
      - Adding a socket send
        You can manually add a socket send element to a socket API performance test.
      - Adding a socket receive element
        You can manually add a socket receive element to a socket API performance test.
    - Verifying application behavior
      Add the different verification points to verify the responses in a socket test.
    - Merging socket send and receive elements
      With the Organize wizard, you can merge consecutive send or receive elements that use the same connection to improve the clarity of your socket test.
    - Changing multiple socket send and receive elements
      You can perform global changes to multiple send and receive elements in a socket test.
    - Splitting a socket test
      After you record a test, you can split it into smaller tests. Splitting tests enables you to create modular building blocks of smaller tests and combine them to make bigger tests. The original test is unchanged. You can recombine these building blocks in a schedule, including loops and conditions.
    - Using custom code to specify an end policy
      You can write a custom Java™ class to specify when a socket receive element stops receiving. This offers the most flexibility, but requires that you write your own Java class using the HCL OneTest™ Performance extension API.
    - Using custom code to manipulate data
      You can write a custom Java™ class to manipulate data in a send element. This offers flexibility for injecting data in test, but requires that you write your own Java class using the HCL OneTest™ Performance extension API.
  - Editing Kerberos tests
    You can change the Kerberos realm, user name, and password when editing tests.
  - Adding test elements
    You can add a variety of elements to a test, such as transaction blocks, IF-THEN conditions, loops, and comments.
  - Searching within tests
    Search request data or response content by right-clicking in the data or content and selecting Find. To search for specific element types and to display the results in a table, click Select. For a still more powerful search and replace, use the Test Search function.
  - Exporting a test
    To share the test scripts with manual testers or reviewers who do not have the workbench, export the test scripts to text files. You can export one file at a time.
  - Copying test assets with dependencies
    You can export test assets, and then import them into another project or workspace without losing any dependencies. Test assets include projects, schedules, and tests. You can export and import test assets to collaborate with other testers.
  - Disabling portions of a test
    When you disable portions of a test, you can still see the disabled portion, but it is not executed during a run. You can also disable portions of a schedule by using the following procedure.
  - Running test elements in random order
    You can record multiple user scenarios in a test and then run each scenario in a random order. To do this, you put each scenario under a random selector and then select the proportion of time that the scenario should be run.
  - Renaming test assets
    As your test assets increase and become more complex, you might want to rename them. Use the Eclipse Rename function or save the assets under a different name.
  - Deleting test assets
    As your test assets grow and become more complicated, you might want to delete the assets that you no longer use.
  - Debugging custom code for tests and compound tests
    If you have custom code added to a test or a compound test, you can debug the custom code for any errors by clicking the Debug button.
  - Providing tests with variable data (datasets)
    You can produce more realistic tests by changing them to use datasets. During execution, a test that uses a dataset replaces a value in the recorded test with variable test data that is stored in the dataset. This substitution allows each virtual user to generate a different request to the server.
  - Test variables
    A test variable is a user-defined, name-value pair that stores and refers to information throughout a test and between tests.
  - Correlating response and request data
    For a test to run correctly, a request that is sent to a server might need to use a value that was returned by a previous request. By ensuring that this data is correlated accurately, you can produce better performance tests.
  - Data transformation
    You can transform HTTP application specific data such as binary data and encoded data to a more readable format to use data correlation.
- 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.
- Emulating workloads
  You emulate a workload by creating a schedule and adding user groups/rate runner groups, tests, and other elements to it.

Adding a socket close

You can manually add a socket close element to a socket API performance test.

Before you begin

In a performance test, socket close elements close the connection to a server. A socket close element relates to a specific socket connection.

Ensure that for each socket connection, there is a corresponding socket close. If not, during the test run, the operating system can run out of socket handles, causing the test to fail.

Procedure

Open the performance test in the test editor.
In the Test Contents area of the test editor, right-click the test node, and click Add > Socket Close.
In the Test Element Details section, click Change and select the socket connection that you want to close.
You can specify a Think Time delay before the test establishes the connection.

Results

After you have closed a connection, you can no longer send or receive data from that connection. If any test elements use a connection after the close element, they are flagged with an error in the test editor.