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…
Uncategorized, loadurnner
loadrunner
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…
loadurnner, qtp, ruby
function, loadrunner, qtp, rand, random
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…
loadurnner
function, loadrunner
At the moment, I’m using laodrunner to performance test a web application. The application, like all, has an array of regular error messages that appear. All scripts should have some form of error checking/handling, but as there is limited re-usability in scripts for performance/load testing, I believe its best to keep it to a minimal. It’s a ‘run and throw away’ style of scripting, there is no performance regression suite, even though you could go through several phases of an application, and performance testing would be required in each phase, more often than not, the application has changed so much, that a need to re-record and re-correlate is required. Therefore you would be forced to throw away the error checking logic that you spent hours defining == waste of time and $$.
Sure, some level of error checking is needed to determine the source of failure, when an error occurs, and being able to easily identify the client side error messages helps eliminate many tangents. I’ve seen performance scripts with complex error handling, that usually have taken hours to code, expensive time which the client is paying for and code which could possibly never be executed. So it only makes sense to KISS.
Read more…
loadurnner
check, content, loadrunner, web_global_verifcation
