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.
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.
Test data sources overview
Use the Test Data Sources window to add or change data correlation for any supported test element.
Built-in Datasources
You can use built-in data sources instead of creating custom data sources to substitute the recorded values. The Built-in Datasources in the Test Details section displays the data sources that have been used and unused. You can also modify their properties from a location.
Creating a Sequential Number datasource
You can create a sequential number datasource in HCL OneTest™ Performance to assign unique sequential numbers to all the virtual users in a test. This datasource can generate unique integers or floating point numbers for the users.

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.
  - 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 correlation overview
      A request can include data that was returned in the response to a previous request. Associating data in this manner is called data correlation.
    - Viewing data correlation
      You can switch between viewing all test elements in the test editor and viewing only elements related to data correlation in the test editor. Viewing only data correlation elements makes it easier to add and remove substitutions.
    - Data correlation rules overview
      You can use the data correlation rules editor to customize how data is correlated. You can control how references and substitutions are generated in tests, and store these rules so that you do not have to manually correlate data in every test that you record against a particular application.
    - Test data sources overview
      Use the Test Data Sources window to add or change data correlation for any supported test element.
      - Correlating a request value with test data
        If a test runs without error but does not generate the results that you expect, you might need to correlate a value in a request with other test data.
      - Substituting request content with file contents
        You can substitute the content portion of a protocol request with the contents of a file. This feature is only supported in certain sections of a test, depending on the protocol. For example, HTTP tests support file content substitution only in the POST data section of a request. SOA tests support file content substitution for MIME and DIME attachments, XML node values and fragments, and text content. File content substitution works in the same manner as other substitutions. All standard test data sources such as test variables, datasets, and references can be used. The data from the source is treated as a full path to a file. The file is opened, its contents are read, and then those contents are used in the substitution.
      - Built-in Datasources
        You can use built-in data sources instead of creating custom data sources to substitute the recorded values. The Built-in Datasources in the Test Details section displays the data sources that have been used and unused. You can also modify their properties from a location.
        Creating a Random Number datasource
        You can create a random number datasource in HCL OneTest™ Performance to assign unique random numbers to all the virtual users in a test. This datasource can generate unique integers or floating-point numbers for the virtual users in the schedule. You can choose to distribute the numbers of the virtual users or clients in a uniform, normal, or negative exponential way.
        Assigning random numbers to virtual users
        When a recorded value in the test contains variable data, and you want to substitute that value with a random number during the schedule run, you can assign random numbers by using a Random Number built-in datasource.
        Creating a Sequential Number datasource
        You can create a sequential number datasource in HCL OneTest™ Performance to assign unique sequential numbers to all the virtual users in a test. This datasource can generate unique integers or floating point numbers for the users.
    - Reference or Field Reference overview
      A Reference, which is in response data, points to a specific value that you want to use in a subsequent test location, generally a request. Whereas a Field Reference points to an entire block of test data.
    - Correlating multiple fields in a test
      Some tests are structured in such a way that you must correlate data for multiple fields.
    - Guidelines for adjusting data correlation
      When you run a test, you might notice that the server is not under the expected load or that your database is not being updated as expected. Incomplete or incorrect data correlation can cause these problems.
    - Finding data correlation errors
      You can use the Potential Correlation Errors view to find missing or incorrect data correlations.
    - Disabling data correlation
      You can disable a data correlation source or a substitution site. When you disable a data source, none of the substitution sites that use the source will be correlated when you run tests. When you disable a substitution site, only that specific substitution site is disabled. Other substitution sites that use the same reference will be correlated when you run tests. You can also disable data correlation entirely for subsequent tests that you record.
    - Recorrelating test data
      If you disabled automatic data correlation before recording a test, you can regenerate the test with automatic data correlation enabled.
  - Data transformation
    You can transform HTTP application specific data such as JSON data, 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.

Creating a Sequential Number datasource

You can create a sequential number datasource in HCL OneTest™ Performance to assign unique sequential numbers to all the virtual users in a test. This datasource can generate unique integers or floating point numbers for the users.

Before you begin

You can use the sequential built-in datasource option wherever data correlation substitutions are permitted, such as Transactions or Delays.

About this task

You define an initial value that should be assigned to the first virtual user and a step value that is a number by which the current value increments after each retrieval by a virtual user. If initial value is 1 and step value is 5, the workbench generates numbers in the sequence of 1, 5, 10, 15, and so on and each number is mapped to a virtual user. If a test is run on multiple agent machines, the workbench assigns a sequential value to all the users in all the agent machines.

You can also assign a full sequence of numbers of one virtual user. The sequence number increments in the request for each time the request in the multi-request generator is executed.

Procedure

In the Test Contents area of the test, click an element in the test where data correlation substitution is permitted, such as a transaction name or delays.
In the Test Element Details area, right-click the name of the element and click Substitue > Built-in Datasources.
In Built-in Datasource Selection Wizard, click Sequential Number and click Next.
Assign a name for the datasource.
In Initial Value, type a number to be assigned to the first virtual user.
In Step Value, type a number.
In Formatting Options, you can format the number in the manner you want to use.
Optional: To assign a full sequence of numbers to one virtual user, select the Execute for individual user check box.
Optional: To substitute the built-in datasource every time with a new value for the requests, select the Get new value each time used check box.
Click Finish.
Save and run the test.

Results

After you add the test to a schedule and run the schedule, the test log displays each element name where the datasource is applied with the unique sequential number assigned to the virtual user.