Share this page

# Working with TruClient 2.0

This topic describes the process for creating and working with TruClient 2.0 scripts.

In this topic:

## Developing a script

The TruClient UI provides the environment you work in to record, replay, enhance, and debug your Vuser scripts. These activities are not separate. For example, to solve a problem found while debugging during replay, you might enhance the script by making some steps conditional, or by recording additional steps in the script.

The UI has two major windows:

- Development window. This is the heart of the interface, containing the tools you need to develop your TruClient scripts. It provides a graphical view of the script steps.

- Application browser window. This contains your selected browser, where you develop and replay your scripts interactively.

Tip: You can resize and reposition these windows as you want.

See the following sections for more information on developing and running your scripts:

Action | Description
--- | ---
Get started | Learn about the Development window UI and working with script steps, and configure global settings for your scripts. For details, see Development window.
Record | Your actions are recorded and converted into steps while you perform a business process on the selected browser. For details, see Record scripts.
Replay | You must replay your script at least once, so TruClient can perform some background tasks. You will probably replay more than once, while you debug the script. For details, see Replay scripts.
Enhance | TruClient records exactly the actions that you take. However, when testing you may want the test to run differently than you recorded it. For example, you may want to run some steps only if a condition is true, or to vary the data you enter in the application. In addition, the data collected may not be what you need. You may need to collect performance data separately on different steps or different groups of steps, rather than on the entire business process. For details, see Enhance scripts.
Program | Functionality is provided to implement advanced scripting requirements for your scripts. For details, see Programming for scripts. For details on the available API functions, see TruClient 2.0 - Web functions in the VuGen Function Reference.
Load test | Your scripts can be used for performance and load tests in multiple OpenText tools, including OpenText Professional Performance Engineering, OpenText Enterprise Performance Engineering, and OpenText Core Performance Engineering. They can be run on Windows-based or Linux Ubuntu-based load generators. For load testing tips, see Load test with TruClient scripts.

## Script structure

All TruClient scripts contain the following elements:

Steps | Steps are structures that contain a user action to perform, object identification, the point where the next step can start, and other data. There are several types of steps. Step type examples include: One user action and the application response. A function call. A flow statement that may contain other steps. For example, a for loop. For details, see Step structure.
Actions | An action contains a series of steps you want to test as a sequential set. An action generally corresponds to a business process for your application, that is, a task users might perform. A business process can be very short and specific, like logging in, or larger, like a sequence that starts with a search and ends with a purchase. For details, see Script actions.
Run Logic | The flow of your script, meaning the order actions run in and the number of times they run. For details, see Run logic.

You can think of steps as program statements, actions as sub-routines, and the run logic as the main routine.

## See also

- Development window
- TruClient 2.0 - Web protocol

https://admhelp.microfocus.com VuGen,Professional Performance Engineering,Performance Engineering for Developers 8942
Tips to improve your search results... OpenText™ Virtual User Generator Help Center OpenText™ VuGen Help 26.1-26.3 All View Local Help Center View Online Help Center Version: