Today, I’m going add one more tutorial in the LoadRunner section. Below are some useful tips to replay a HP Mercury's LoadRunner script for Citrix protocol while doing performance testing:Advertisement:
- Set initialization quota: To prevent overloading by multiple Vusers in LoadRunner while connecting, set an initialization quota of 4 to 10 Vusers (depending on the capacity of the server) or apply ramp up initialization using the LoadRunner Scheduler.
- Enable think time: While doing performance testing using LoadRunner; for best results, do not disable think time in the Run Time settings. Think time is especially relevant before the ctrx_sync_on_window and ctrx_sync_on_bitmap functions, which require time to stabilize.
- Set consistency between machines: If you intend to replay the LoadRunner Vuser script on another machine, make sure that the following items are consistent between the record and replay machines: Window Size (resolution), Window Colors, System Font and the other Default Options settings for the Citrix client. In LoadRunner, these settings affect the hash value of bitmaps, and inconsistencies may cause replay to fail. To view the Citrix Client settings, select an item from the Citrix program group and choose Application Set Settings or Custom Connection Settings from the right-click menu. Select the Default Options tab.
- Increase the numbers of Vusers per machine: Machines running Citrix Vusers may be limited in the number of Vusers that can run, due to the graphic resources available to that machine. In LoadRunner, to increase the number of Vusers per machine, open a Terminal Server session on the machine. You relate to this Terminal Server as a new injector machine. To refer to the virtual injector machine from the LoadRunner Controller, use the following format: machine_name:1, machine_name:2, ... using either the machine name or its IP address. Note that sessions on a Terminal server use, by default, a 256-color set. If you intend to use a terminal session for load testing, make sure to record on machines with a 256-color set.
- Changing window names: In some Citrix sessions, the active window name changes while you are recording. If you try to replay the script as is, the LoadRunner's Vuser uses the original window name and the replay may fail. Using the recording options, you can specify a naming convention for the windows in which LoadRunner's VuGen uses a common prefix or common suffix to identify the window.
- For example, if the original window's name is "Application 1" where the name changes during application's run to "Application 1", you can instruct LoadRunner's VuGen to use the common prefix only, "Application".
Alternatively, you can modify the window names in the actual script after recording. In the Script view (View > Script view), locate the window name and replace the end of the window name with the wildcard notation, *. For example, ctrx_sync_on_window ("Application*", ACTIVATE, ...);.