Home
Test Execution Specialist Guide
This guide describes tasks that you can perform on schedules, test execution with custom code, and Extending HCL OneTest™ Performance to support other protocols. This guide is intended for testers or test execution specialists.
Running schedules with performance testing
After you have added the user groups, tests, and other items to a schedule, and you are satisfied that it represents a realistic workload, you run the schedule.
Adjusting delays in HTTP tests
You can configure HTTP tests to use client-side processing delays. Client-side processing delays wait for the first character or last character that is received in a response for a previous request in order to better emulate the work done on the client computer. You can also scale the recorded delays in HTTP tests to change the rate at which a test runs.
Configuring HTTP client delays
You can configure delays for HTTP requests to emulate client-side processing delays. Applications that use client-side Javascript, such as Web 2.0 applications, often incur significant delays due to processing done on the client. You can emulate this client-side processing in HTTP tests. Running an HTTP test too quickly can cause unexpectedly low page response times to be reported, and can generate excessive load on the server under test.

Test Execution Specialist Guide
This guide describes tasks that you can perform on schedules, test execution with custom code, and Extending HCL OneTest™ Performance to support other protocols. This guide is intended for testers or test execution specialists.
- Running schedules with performance testing
  After you have added the user groups, tests, and other items to a schedule, and you are satisfied that it represents a realistic workload, you run the schedule.
  - Running a local schedule or test
    You can run a test locally or a A schedule, in this context, is used to refer to both VU Schedule and Rate Schedule. on remote locations with a default launch configuration.
  - Running a long run mode SAP GUI test
    When running a SAP GUI test that could last for many hours and could use up the operating system resources, you can choose to run the test with the Long Run Mode process. It is an external process that restarts automatically after the specified number of SAP sessions are over. So, tests of longer duration tests are more likely to finish.
  - Running long duration Citrix tests
    When tests exceed many hours, resource consumption issues can cause problems for the Citrix clients. The long run mode increases the reliability of long duration tests with the Citrix protocol by running the test using multiple processes.
  - Testing with Docker images
    HCL OneTest™ Performance, HCL OneTest UI, and HCL OneTest Performance Agents are available for download as Docker images. You can use them to fulfill the continuous testing aspects of your DevOps lifecycle.
  - Adjusting delays in HTTP tests
    You can configure HTTP tests to use client-side processing delays. Client-side processing delays wait for the first character or last character that is received in a response for a previous request in order to better emulate the work done on the client computer. You can also scale the recorded delays in HTTP tests to change the rate at which a test runs.
    - Configuring HTTP client delays
      You can configure delays for HTTP requests to emulate client-side processing delays. Applications that use client-side Javascript, such as Web 2.0 applications, often incur significant delays due to processing done on the client. You can emulate this client-side processing in HTTP tests. Running an HTTP test too quickly can cause unexpectedly low page response times to be reported, and can generate excessive load on the server under test.
    - Adjusting client delays for all tests
      To ensure consistency in client processing delays for all the tests in a user group, starting from 9.1.1.1, you can override the client processing delays of the tests and set it in the schedule.
    - Overriding the HTTP connection timeout value
      By default, HTTP page connections use a timeout value of 190 seconds, which might not be sufficient for some applications. You can override the page connection timeout value for specific pages in a test.
    - Overriding Websocket response timeout value
      By default, the timeout value for WebSocket responses is 240 seconds at the test level. This value might be insufficient or in excess for different applications. You can customize the timeout value for specific responses.
    - Playing back HTTP tests faster than the recorded rate
      If the client computer used for recording an HTTP test was slower than required, or if you want to emulate a faster client computer, you can increase the playback rate without altering the actual values in the recorded test by reducing the client delays proportionately. Similarly, you can slow down the client by increasing the client delays.
  - Setting a launch configuration
    Instead of using the default launch configuration, you can specify the file name for the execution results, the name of the folder for the execution results, and, for a test, the number of users.
  - Running a configured schedule
    If you do not use the default launch configuration, you can configure the schedule and then run it.
  - Configuring multiple host names for a location
    You can run several locations on the same computer by configuring multiple host names for a location. This configuration affects all tests running at that location; all tests will run with the configured port.
  - Automating tests from command line
    You can run a schedule from the command line. You can also set preferences to export results after the run completes from the command line or from the workbench. Together, these features let you run tests and analyze results without opening the workbench. You can even write scripts to process the exported results.
  - Controlling caches size
    If you use an infinite loop and the number of cached responses in a test increases exponentially, you can set a limit to cache for a user group in the schedule.
  - Increasing memory allocation
    The virtual users that access your web server require memory to prepare requests, send requests, and receive responses. Because the amount of memory is not automatically set on remote computers, you might receive an out-of-memory error. To correct this situation, increase the memory allocation for that computer.
  - Controlling execution of web analytic reports
    When a schedule is in the running state, you can perform the following actions from the web analytics reports to cater to your need.
  - Debugging HTTP tests
    If a test does not behave as expected during playback, you can use the protocol data and test log to assist in debugging the test.
  - Debugging Citrix tests
    The Citrix dashboard is an optional panel that displays detailed information and control commands for each virtual user during the run of a schedule. This is useful for debugging your tests and allows you to pause, interact, resume, or stop the execution of individual virtual user sessions.
- Extending test execution with custom code
  You can extend how you run your tests by writing custom Java™ code and calling the code from the test. You can also specify that results from the tests that are affected by your custom code be included in reports.
- Extending HCL OneTest™ Performance to support other protocols
  The HCL OneTest™ Performance Extensibility Software Development Kit (SDK) enables you to create extensions to support testing new protocols without modifying the core product code. You can create an extension that provides functionality for testing other protocols in addition to the HTTP protocol support that is standard in HCL OneTest Performance.

Configuring HTTP client delays

You can configure delays for HTTP requests to emulate client-side processing delays. Applications that use client-side Javascript, such as Web 2.0 applications, often incur significant delays due to processing done on the client. You can emulate this client-side processing in HTTP tests. Running an HTTP test too quickly can cause unexpectedly low page response times to be reported, and can generate excessive load on the server under test.

About this task

To remove request delays from response times for all the tests, click Window > Preferences > Test > Test Generation > HTTP Test Generation and select the Remove HTTP request delays from response times.

To remove request delays from response times for a specific test, in the Test editor select HTTP Options and clear the Remove HTTP request delays from response times check box.

Procedure

To configure HTTP client delays:

In the Test Navigator, browse to the test and double-click it.
The test opens.
Click the name of the test.
Click HTTP Options.
On the HTTP options page, select Enable new client processing delays.
Under Test Contents, select the request on which to enable client processing delays.
Under Test Element Details, click the Advanced tab.
Under Client Processing Delay, click Request.
A test editor window opens, listing the previous requests in the test.
Select the request to wait for, and then click OK.
For Release when, select First Character Received or Last Character Received.
Type any Additional delay to add in milliseconds.