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.
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.
Managing HTTP information in the Protocol Data view
Several actions can be performed on the text displayed in the Protocol Data view. You can save the text from the Protocol Data view pages to a text file for use in other applications. You can search for text in the protocol data. You can compare the data retrieved during a run with the recorded data from an HTTP test. Typically, you compare a request or response from the test log to its corresponding data in the recorded test. You can also compare requests or responses from different virtual users in one test log.

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.
  - 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.
    - HTTP debugging overview
      If a test is not behaving as expected, you can use the Protocol Data view to debug the test. This view can be useful after you record a test, after you make changes to an existing test by adding datasets or data correlation, or after you make changes to the system under test.
    - Debugging HTTP Data Correlation Errors
      Data correlation errors are very common and sometimes complex to fix. A dedicated Eclipse-based perspective can guide you to debug data correlation errors.
    - Watching a virtual user during a test run
      The Browser page in the Protocol Data view displays browser results during an individual HTTP test run. The Browser page displays each page in real time.
    - Watching a virtual user during a schedule run
      During a schedule run, you can select any virtual user and watch that user's real-time browser. Watching the real-time browser lets you investigate the status of individual virtual users while they are running. You can determine whether a run is valid despite the occurrence of individual virtual user failures.
    - Replaying a virtual user after a run completes
      After you create a schedule, run it with a small number of users and watch their activity to verify that the schedule is behaving as expected. You can compare the visual data that is rendered as well as the events that are logged for each user.
    - Viewing the playback summary of a virtual user
      The Event Log page in the Protocol Data view provides a summary of what happened during an HTTP test run. A complete summary is always available for a test. The information available for a schedule depends on its logging level.
    - Inspecting HTTP test logs in the Protocol Data view
      To verify that a test is performing as you intend, use the Protocol Data view, which displays the HTML details that were generated during a schedule run. If problems occur in a test run, you can also compare the data retrieved during the run with the recorded data.
    - Managing HTTP information in the Protocol Data view
      Several actions can be performed on the text displayed in the Protocol Data view. You can save the text from the Protocol Data view pages to a text file for use in other applications. You can search for text in the protocol data. You can compare the data retrieved during a run with the recorded data from an HTTP test. Typically, you compare a request or response from the test log to its corresponding data in the recorded test. You can also compare requests or responses from different virtual users in one test log.
  - 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.

Managing HTTP information in the Protocol Data view

Several actions can be performed on the text displayed in the Protocol Data view. You can save the text from the Protocol Data view pages to a text file for use in other applications. You can search for text in the protocol data. You can compare the data retrieved during a run with the recorded data from an HTTP test. Typically, you compare a request or response from the test log to its corresponding data in the recorded test. You can also compare requests or responses from different virtual users in one test log.

Procedure

To export HTTP data from the Protocol Data view to a text file:

In the Test Navigator, right-click the results that you want to export, and click Display Test Log. The results have the same name as the test or schedule with a timestamp appended.
In the editing area, click the Protocol Data tab to open the view.
Click the button that corresponds to the data that you want to export: Request, Request Headers, or Response Content.
You cannot export data from the Browser page.
Optional: To export only a portion of the text, select the text, and click the appropriate option from the menu:

Select one of the following options from the toolbar:

Option	Description
Save to protocol data	Saves the entire text on the page to a text file within or outside of your workspace.
Copy to clipboard	Copies the entire text on the page to the clipboard.
Compare to clipboard	Compares the entire text on the page to the contents of the clipboard. To compare the playback data with the recorded data, view the protocol data in the test log and select Copy to clipboard. Then, use the element link in the details section of the test log to navigate directly to the associated recorded element, and select Compare to clipboard.
Find	Searches the data in that test log page. You cannot replace data in the test log.

The text is saved in the default (locale-specific) encoding that is set on your computer. Keep this default locale setting unless your text contains non-Latin characters.

Optional: Click the menu on the toolbar to save the file in Unicode.