Posts Tagged ‘Denamik LoadGen’

"true" client side testing best practices

Written by Ingmar Verheij on June 9th, 2011. Posted in Performance testing

iRobot NS5When performing a LoadTest user actions are simulated. This implicates that mouse or keyboard actions are executed based on a script, based on a scenario, and that the script waits for a response on the screen.

The response on the screen can be determined using API’s giving information about windows present, or the controls on the windows. For instance: the script waits until a window is active with the caption "Microsoft Word".

Another way of determing if a response is given is by comparing the content of the screen with a bitmap. For instance: the script waits until an empty document is displayed in Microsoft Word.

The difference between the two techniques is that a window caption is present right when the application is launched (even if the application is still loading) while the content on the screen is more simular to the way users interact in a session. So looking at a screen region is more accurate, it prevents assumptions (best practice #9 in loadtesting best practices) like "how much time should we wait between lauching an application and clicking on a menu?”.

In this article I will be discussing some best about practices about “true” client side testing (best practice #12 in loadtesting best practices).

Stresstest your printer drivers

Written by Ingmar Verheij on November 6th, 2009. Posted in Performance testing, Printing

A few days ago I wrote an article about the issues with printer drivers in a multiuser environment. In this article I advised you to test you’re printer drivers in a acceptance environment, preferably with real users testing. This can be achieved with a LoadTest / StressTest tool like the Denamik LoadGen, which is free up to 25 users. And since testing with 10 users is enough to stress a driver, there’s no need to buy a license.

Today I would like to tell you how this is done, step-by-step.

The goal
We’re going to try to use the printer environment as realistic as possible, but where focusing on the worst case scenario. Because where trying to find out whether the printer driver is functioning correct when multiple users are printing, where going to simulate that a number of users are printing to printers using the same printer driver.