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 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.
Adding elements to a Citrix test
You can add a variety of elements to a test, such as user input actions, comments, loops or conditions.
Viewing a mouse sequence
You can use mouse sequences to view complex mouse movements on the screen.

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.
    - Citrix test editor overview
      With the test editor, you can inspect or customize a test that you recorded.
    - Citrix synchronization overview
      During the run of a Citrix session, the test uses window events or image recognition to ensure that the correct user input actions are maintained on track with the application events coming from the Citrix server.
    - Verifying application behavior
      To check the expected behavior of the application during a Citrix performance test, you can add verification points at strategic points in the test. You can use window verification points to check that a specific window opens during the test, regardless of its contents, or you can use image synchronization to verify the displayed contents. During the run, verification points produce a pass, fail, error, or inconclusive status in the Citrix Verification Point report. You can also measure response times between two test elements.
    - Adding elements to a Citrix test
      You can add a variety of elements to a test, such as user input actions, comments, loops or conditions.
      - Editing a mouse action
        You can edit mouse actions to manually specify how the mouse interacts with the Citrix server.
      - Viewing a mouse sequence
        You can use mouse sequences to view complex mouse movements on the screen.
      - Editing a keyboard action
        You can edit keyboard actions to manually specify how the keyboard interacts with the Citrix server.
      - Editing a text input
        You can edit text inputs to replace a sequence of keyboard events with text strings that are easier to handle as dataset variables or references.
      - Synchronizing tests with screen areas
        Image synchronization enables Citrix performance tests to keep track of the contents of a screen area during replay instead of focusing only on window events.
      - Manually adding an image synchronization
        You can manually add an image synchronization element to an existing test to ensure that the test synchronizes correctly or to add a verification point. To do this, you must create the image synchronization element, and then perform a single run of the test to retrieve the image hash code or text detected by optical character recognition (OCR).
      - Adding values to an image synchronization
        You can replace or add alternative values in an image synchronization element so that synchronization is not restricted to the exact recorded image. Alternative values can also be useful in updating the test if the behavior of the application changes.
      - Using custom code with a Citrix test
        You can write custom Java™ code to expand the functions of HCL OneTest™ Performance.
  - 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 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.

Viewing a mouse sequence

You can use mouse sequences to view complex mouse movements on the screen.

Before you begin

Mouse sequences provide a graphical view of a series of mouse move events. This is particularly useful when a large number of mouse move events are meaningful to the application. For example, drawing the letter e in a paint program is represented as a mouse down event, a mouse sequence, and a mouse up. In the test editor, the sequence graphically displays how the letter e is drawn in the application. If any screen captures were taken during the recorded session, the sequence will be shown over the screen capture.

In most cases, you will rely on the mouse sequences that were recorded with the test. However, in some cases, you might want to manually refactor mouse events into sequence.

Note: Because Citrix tests contain low level user input and synchronizations, minor changes can prevent the test from working. When editing these tests, you must ensure that they are functionally identical.

Procedure

Open the test in the test editor
Expand a window event and select the sequence in the Test Contents area.
In the Test Element Details area, you can view the following information:

Display mouse sequences for

This option specifies how you want to display previous, current, or all mouse sequences in the current mouse sequence:

Current® sequence

Only the current mouse sequence is displayed in the test editor. This option is selected by default.

Previous and current sequences

The current mouse sequence is displayed with any previous mouse sequences.

All sequences

All mouse sequences are displayed simultaneously.

Fit screen to visible area

Select this option to adjust the display of the mouse sequence to the available area in the test editor. If disabled, the screen capture will be the actual size, which might require scrolling. This option is enabled by default.

Screen capture area

This area represents the mouse movements on the screen. If a screen capture was recorded, it is displayed in the background. Mouse sequences are displayed as specified.