Monthly Archives: February 2009


error checking in loadrunner

There is no real point in running a script if you’re not going to check and handle for errors. In my opinion, this is what defines a good loadtester/automator from a fake one. I have seen many fake testers, who are palmed off into our industry as experts, but can only record and playback. But that’s a whole different gripe I have.

I’ve spent the last few weeks discussing this topic in detail with my manager, and senior mentor Nick Singh from JKVine and together we have come up with a ‘framework’ (buzz word) that is not too time consuming and has proved to be very successful.

read more »

loadurnner Uncategorized

loadrunner error :: The user files were not transferred to the local load generator

This occurs When trying to run a load test on a remote load generator.
I have my script on a network location, as its easy to share with my team.
The script utilizes the loadrunner parameters, and the dat files are stored on the same network location, in another folder of course.
Two errors actually occur
1.Error: The user files were not transferred to the local load generator
2.One or more of the script’s files have illegal names.It is possible that two files are using the same name and directory

Unfortunately for me, this error does not give me much information, like most of mercury/hp’s errors, it leaves me on a wild goose chase. The reason to the problem is quite bizarre, and very strange. But there is a way to fix it.

read more »

loadurnner qtp ruby

random numbers & words

The random function is extremely useful, no matter the language or application. I personally utilise it a lot, between many different languages. I have found, however, that it is one of those functions I always seem to forget how to do, and find myself re-learning it again.
I find the issue when I change from, be it, ruby, to qtp to loadrunner to winrunner. do while loops, counters, and arrays are all quite standard, but random, well, it gets me every time.

read more »


creating loadrunner functions

As we all know, creating functions has its benefits, and the rule of thumb is that if you’re going to use something more than once, its always better to create a function and call that function. Loadrunner is no different.

This post is quite a simple technique that is probably very well known in the community, so I’ll keep it short.

read more »


run time settings :: scheduling & pacing

I have found that run time settings give me the most grief when planning a run. In particular, pacing, think time and scheduling. After calculating the amount of users and the quantity of transactions vs the duration, I need to do some simple mathematical calculations to work out the pacing of the vusers, and the ramp up time. If you’re like me, you hate spending 20 mins with a calculator working it out. So a colleague of mine built a spreadsheet that we just plug figures in and it does the rest.

I’ve built on this spreadsheet, given that during shakeout, I do not run 100% of user load on the system, instead I may run 10% or 20% or even 50%. Given this, once I have the 100% figures, I don’t want to re-calculate everything at a reduced rate, that’s just annoying…

read more »