Home
Tutorials
This section contains the tutorials which explains the main features of HCL OneTest™ Performance.
Performance test a Citrix application
The movies in this tutorial show you the main features of using HCL OneTest™ Performance for testing applications running in a Citrix XenApp environment. The tutorial requires Flash Player to view.
Module 1: Creating projects and recording user actions
In this module, you will learn how to create projects and record user actions for testing. The second part of this module will help you to build an understanding of a recorded test.
Lesson 1.1: Recording a Citrix performance test
In this lesson, you learn how to create a test project and record user actions in Citrix XenApp.

Tutorials
This section contains the tutorials which explains the main features of HCL OneTest™ Performance.
- Performance test a Web application
  The movies in this tutorial show you the main features of HCL OneTest™ Performance. The tutorial requires Flash Player to view.
- Performance test an SAP application
  The movies in this tutorial show you the main features of HCL OneTest™ Performance for testing applications on SAP servers. The tutorial requires Flash Player to view.
- Performance test a Citrix application
  The movies in this tutorial show you the main features of using HCL OneTest™ Performance for testing applications running in a Citrix XenApp environment. The tutorial requires Flash Player to view.
  - Introduction: Performance test Citrix applications
    This tutorial is designed to introduce you to performance testing applications running on Citrix XenApp.
  - Module 1: Creating projects and recording user actions
    In this module, you will learn how to create projects and record user actions for testing. The second part of this module will help you to build an understanding of a recorded test.
    - Lesson 1.1: Recording a Citrix performance test
      In this lesson, you learn how to create a test project and record user actions in Citrix XenApp.
    - Lesson 1.2: Understanding a recorded test
      In this lesson, you become familiar with your recorded test.
    - Module 1 summary
  - Module 2: Editing a Citrix performance test
    In this module, you will see how to edit your recorded test to include verification points and response time measurements.
  - Module 3: Representing workloads
    In this module, you will see how to create schedules that represent a typical workload for your Citrix server.
  - Summary
    This tutorial has taught you the basics of the HCL OneTest™ Performance Extension for Citrix Presentation Server. You have learned how this product provides the following functions and features:

Lesson 1.1: Recording a Citrix performance test

In this lesson, you learn how to create a test project and record user actions in Citrix XenApp.

About this task

The most convenient way to create a new test in HCL OneTest™ Performance is to record a Citrix session. The recording contains mouse and key strokes as user input actions and window events as responses from the Citrix server.

Because of the way the recorder works, consider these issues during the recording:

Set up your application so that all actions are repeatable. For example, turn off "tips of the day," ensure that any file already existswarnings are consistent, and avoid using dynamic menu items such as recent documents.
Ensure that mouse movements are clearly decomposed. The recorder does not record mouse wheel scrolls.
Use specific Microsoft® Windows® accounts for performance testing that have limited potential for data loss if there are errors or synchronization failures during the test run.

For more Citrix recording tips, see Citrix performance testing guidelines.

The recorder synchronizes user actions and window events automatically so that the generated test waits for a window event before triggering the next user input. In some cases, however, you must manually add synchronizations. For example, add synchronizations when screen updates do not result directly from a user action. These synchronizations tell the test to wait for a specific window, text, or graphic to open on the screen before running the next user input.