Using OpenText Functional Testing tests

OpenText Functional Testing enables you to create complex tests that examine the full spectrum of your application's functionality. You can integrate these tests into a Controller load testing scenario in the form of GUI Vuser scripts.

About GUI Vuser scripts

GUI Vusers enable you to measure and monitor end-to-end user response times while your client/server system is under load. A GUI Vuser emulates the complete environment of a human user.

For example, a human user sits at a machine, operates applications using the keyboard and the mouse, and reads information on the machine's monitor. Similarly, a GUI Vuser runs on its own machine and operates applications. A GUI Vuser can be programmed to read and act on information that appears on its machine's display.

Suppose that you have a bank server that services many automatic teller machines (ATMs). You could create a GUI Vuser script that:

Opens the ATM application
Enters an account number
Enters the amount of cash to be withdrawn
Withdraws cash from the account
Checks the balance of the account
Closes the ATM application
Repeats the process

The actions of each GUI Vuser are described in a GUI Vuser script. You use OpenText Functional Testing to create GUI Vuser scripts.

You monitor and manage GUI Vusers using Controller. For instance, you can use Controller to run, pause, or view Vusers, and to monitor scenario status.

Note: You cannot use VuGen to run a GUI Vuser script. You use Controller to run a GUI Vuser script as part of a scenario; you use OpenText Functional Testing to run a GUI Vuser script in standalone mode.

GUI Vuser technology

GUI Vusers measure real end-to-end response times. End-to-end response times represent the total time that a user waits for a response after submitting a request. End-to-end response times include GUI response times as well as network and server response times.

Using GUI Vuser scripts for load tests

GUI Vuser scripts, that have been designed and debugged in OpenText Functional Testing can be used as the basis of your load test in Controller.

The main uses of running the tests in Controller are:

To check how your application's functionality is affected by heavy load
To measure the response time that a typical user experiences on the client side while your application is under load (end-to-end response time)

For example, you can add OpenText Functional Testing tests to specific points in a scenario, to confirm that the application's functionality is not affected by the extra load at those sensitive points.

Another advantage of using a GUI Vuser script as part of your scenario is that the GUI Vuser script runs on your screen during the scenario, enabling you to watch the actual steps executed by the Vuser in real time.