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.
Emulating workloads
You emulate a workload by creating a schedule and adding user groups/rate runner groups, tests, and other elements to it.
Working with agents
If you have a significant workload to test, typically a single computer might not be able to process the load efficiently. You need to distribute the load across multiple computers, also called HCL OneTest™ Performance agents. The agents are installed on computers to generate the load on the application.
Configuring ports for agents
If any service, such as an application server, on the workbench computer uses the default port numbers, you can change the port numbers so that agents can communicate through the new port numbers.

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.
- Emulating workloads
  You emulate a workload by creating a schedule and adding user groups/rate runner groups, tests, and other elements to it.
  - Schedule overview
    A schedule is the "engine" that runs a test. However, schedules are much more than simple vehicles for running tests. You can design or emulate the real-life workload by creating various groups and dividing the load across different remote agents that generate load on the application under test. A schedule can be as simple as one virtual user or one iteration running one test, or as complicated as hundreds of virtual users or iteration rates in different groups, each running different tests at different times.
  - Creating a VU Schedule
    You can create a VU Schedule to accurately emulate the actions of individual users.
  - Creating a Rate Schedule
    By creating a Rate Schedule, you can model the different behaviors of how the application is accessed and measure the rate accuracy.
  - Using Application Performance Management in a schedule
    You can use Application Performance Management (APM) in a schedule to enable AppDynamics or Dynatrace applications and enhance the data collection during load testing by adding HTTP headers to the request in your HTTP tests. You can also use APM to monitor the performance of applications.
  - Think time overview
    Think time is a delay in the processing of a request to reproduce the time that a human would take to read or examine the data that is displayed from a previous user action. Think time is calculated from the time that a request is received (that is, the display is complete on the monitor) until the time that the user clicks a key or link to perform an action.
  - Working with agents
    If you have a significant workload to test, typically a single computer might not be able to process the load efficiently. You need to distribute the load across multiple computers, also called HCL OneTest™ Performance agents. The agents are installed on computers to generate the load on the application.
    - Checking status of agents
      Before running a schedule or test, you can check whether the agents are active and connected to the workbench.
    - Configuring ports for agents
      If any service, such as an application server, on the workbench computer uses the default port numbers, you can change the port numbers so that agents can communicate through the new port numbers.
    - Managing logs in deployment directory
      You can choose to delete or keep the deployment directory for agents after schedule execution. By default, HCL OneTest™ Performance does not delete the deployment directory.
    - Configuring the high resolution timer
      You can configure agent computers to use a high-resolution timer when collecting performance data. The high-resolution timer ensures that all measurements are precise to within 1 millisecond.
  - Adding a test to a schedule
    By adding a test to a schedule, in this context, is used to refer to VU Schedule and Rate Schedule, you can emulate the action of an individual user.
  - Adding must run tests
    In a schedule, you can use the Finally block to specify tests that must be run after the main workload is completed, when the last stage duration is expired, or a schedule is stopped manually.
  - Assigning variables
    In addition to assigning variables at the test level, you can assign variables at the schedule, in this context, is used to refer to VU Schedule and Rate Schedule level and User or Rate Runner group level. When you assign variables at the schedule level, all the tests and groups in the schedule can use the variable initial values, if they have the same variable names.
  - Defining performance requirements in schedules
    You can define performance requirements to specify the acceptable thresholds for the performance parameters in a schedule. The performance requirements that you define can also be used to validate the service-level agreements.
  - Repeating tests in a schedule
    By adding a loop to a schedule, in this context, is used to refer to VU Schedule and Rate Schedule, you can repeat a test for a number of iterations and set the rate for running a test. If the loop contains a synchronization point, the synchronization point is released after the first iteration of the loop and stays released for all further iterations.
  - Creating rate generators in user groups
    A rate generator is a workload container that specifies the number of tasks that the virtual testers run in a given time period. For example, you might be testing an Order Entry group that completes 10 forms every hour, or you might be testing a web server that you want to be able to support 100 hits every minute. Use a rate generator to model this time-based behavior.
  - Running tests at a set rate
    To run a test at a set rate, you add a loop to the schedule to control the iteration rate, and then add tests to the loop. The tests, which are children of the loop, are controlled by the loop. If the loop contains a synchronization point, the synchronization point is released after the first iteration of the loop and stays released for all further iterations.
  - Running tests in random order
    A schedule that contains only user groups and tests will run each test in a user group sequentially. By adding a random selector to a schedule, you can repeat a series of tests in random order, thus emulating the varied actions of real users.
  - Adding a transaction to a schedule
    A transaction is a specific group of test elements whose performance you are interested in. When viewing the test results, you can view performance data about any transactions that you have added.
  - Emulating network traffic from multiple hosts
    By default, when you run a schedule, each virtual user has the same IP address. However, you can make each virtual user appear as though it is running on its own host. To do this, you configure IP aliases on the host computer, and enable IP aliasing in the schedule. When you run the schedule, the network traffic will appear to be generated by multiple hosts.
  - Monitoring resource data
    Resource Monitoring is used to capture data, such as processor or memory usage, while running a test schedule. It can provide a comprehensive view of a system under test, to help identify issues. You can monitor data sources from a local or cloud schedule, or from a Service.
  - Resource Monitoring Service
    When you apply load to a system under test, the system's resources are consumed increasingly. If the capacity of the resources does not match the load, you will notice performance degradation in the results. With the Resource Monitoring Service, you can continually observe the health of the system's resources.
  - Monitoring response time breakdown
    You can use response time breakdown to see statistics on any page element that is captured while running a test schedule or imported from historical data.
  - Setting log and statistic levels
    Within a schedule, you set the size and sampling rate of the test log and the problem determination log, as well as the statistics that are displayed during a run.

Configuring port numbers for agents

If any service, such as an application server, on the workbench computer uses the default port numbers, you can change the port numbers so that agents can communicate through the new port numbers.

About this task

By default, the port numbers for unsecured and secured ports are 7080 and 7443. The HCL OneTest™ Performance agents poll the workbench using the non-secure port number. If you want to encrypt the communication between the workbench and agents, select Workbench and agent communication is encrypted using TLS/SSL. HCL OneTest™ Performance then uses the secure port number for communicating with agents. The workbench internally sends the secure port number to the agents via messages exchanged over the non-secure port number.

Note:

If you change the non-secure port number, you must configure the agents to poll the new port number. In the HCL OneTest™ Performance computer, open the majordomo.config file located at installationDir/Majordomo and update the port number.
If two instances of a workbench are opened on one computer, first workbench gets access to port 7080 to communicate to an agent. For the another workbench to access the agent, you must use a different port number.
To work with a dataset, you must ensure that two consecutive port numbers are available. One of the ports is used to communicate between the workbench and agent, and the other is for the dataset server. For example, you must ensure that the port number 7081 is open for the dataset server if the default port number 7080 is used to communicate between the workbench and agent. Similarly, if you use any different port number for communication between the workbench and agent, you must ensure that the next port number is available for the dataset server.

Procedure

In HCL OneTest™ Performance, click Windows > Preferences > Test > Server.
Specify the new port numbers and click OK.

What to do next

You must now update the majordomo.config file for the agents to poll the new port numbers.