Generating Error Snapshots with LoadRunner Controller

LoadRunner Controller throws up errors here and there almost all the time; 99% of these errors are due to either scripting problems or code changes (the other 1% are out of memory exception errors ;))

The errors generated in the Controller are usually enough to figure out what the problem is, however there are times where the errors generated leave one searching for clues like a scavenger hunt.

Then I came across this option in the Controller… “Generate snapshot on error“… hmm, this looks like it could prove very useful for web testing.
Indeed it did. Turns out that every-time an error is encountered in the Controller, a snap-shot of the page the error was encountered on will be saved and stored in the results folder in .html format.


Using Two or More Load Generators with LoadRunner

LoadRunner is a suite of applications designed specifically for performance testing of computer systems.

Put at a very high level, LoadRunner is used to throw load (or Virtual Users in LoadRunner terms) at a system to check for performance counters such as throughput, CPU per transaction etc. LoadRunner supports a variety of different architectures including Web, ERP, CRM and more.

This article details the steps of how to set-up multiple load generators to work with your LoadRunner Controller environment.

There are several drivers for going with this approach:

  • Your load generator may actually sit on the same box as your Controller (design flaw)
  • Your load generator may be a low spec box which maxes out at X number of VUsers
  • You want load to hit the target from multiple machines to introduce threading.
  • etc