Quotium’s WinLoad module for QTest enables performance testing of almost any application without the need for complicated scripting or ‘dll’ calls from the host application.

Winload works differently from protocol script-based tools so that scripting with complicated middleware or protocols can be avoided.

Some applications, such as web-based, lend themselves very well to working at protocol level. However, some such as COM, mainframe, Citrix, or proprietary protocol based applications do not. For these applications the Qtest WinLoad module becomes a very useful and unique solution. With the Winload module, Qtest actually brings a powerful solution to multi-platform, multi-protocol applications testing and monitoring.

WinLoad works on the GUI level. When WinLoad transactions are replayed they are replayed through the user interface of the application. This means that response times measured using WinLoad are more accurate, as they include the time the client application part of the system under test takes to render the raw data received at the protocol level.

The diagram below explains the way the load is generated:

 

 

By using one or more server spec machines as injectors, many instances of the client application can be run concurrently by the Winload agent. The console’s launch pad controls the terminal server sessions and enables the tester to take a real-time view of transactions as they run. QTest then gathers timings and server health stats from the systems under test to detect anomalies and give an accurate report on the results of the load test. We also carefully monitor the injector machines to ensure that they remain in a healthy state and do not cause delay to the transactions for which we are testing.

WinLoad transactions are simply recorded by hitting the record button on the agent. The agent then captures mouse movements, mouse clicks, key strokes and extra control information that is easily entered using the function keys. When replayed, the transaction is synchronised using bitmap captures made during the record process. This is so that the transaction waits until it recognizes something on the screen that it saw during capture. This is essential because when replayed, especially while under load, the application cannot be guaranteed to give the same response times. Therefore, without these synchronisation points, WinLoad may be trying to click on a button that has not yet appeared.

The agent also synchronises automatically on Window events, meaning that we do not have to always put in these bitmap synchronisation points.

The bitmap synchronisation points are especially useful for test applications that do not have window events. For example, a Citrix client is simply displayed as a large bitmap.

The Launch pad (left) enables full visibility of each virtual user in the test. It also allows virtual users to automatically log on with different credentials. During the replay of the test, transactions will be seen running from the launch pad which is a view into the injector machine.

QTest consolidates results from all back end monitoring and from response times into one result set. These correlated results can be viewed for analysis and used to automatically generate reports.

Anomalies are automatically detected from each test results and listed by order of severity with graphical representation for easy analysis, and with indication of possible root cause when applicable.