If you are reading this, I assume that you have some experience in performance testing and that you have executed load tests using HP's LoadRunner software. If you have, I am sure you must have come across errors while running a load test and the following picture may look all too familiar -
One thing that I would like to point out here is that the errors have been forcefully encountered, and I can do a simple HP Web Tours flight booking script pretty well :)
What we usually do when we hit such a scenario is click on the 'errors' to see what is failing.
This is perfect because this helps us identify errors in scripts and rectify them before the next load test run. So, if there are a more than few errors, it becomes difficult to remember them all and its easy to make a note of it to work on it later. All is well, until you close Controller. Because after that, you no longer have easy access to the errors encountered. Also, if you are using Performance Centre, the moment the load test finishes, these details are whisked away. The next step is Analysis, which is a wonderful tool, but it leaves a lot to be desired in the errors section. It just shows you a few graphs that do not give all the error details. One option is to enable logging on error and actually going inside each users log file in the raw results folder to get the details of the errors encountered. But if you have a large number of users, even this method is not really feasible.
This is where KAOS-LREA can help you. It does all the heavy lifting for you, just point it to the location of the .lrr file in the results directory (in case you are using Performance Centre, download the RawResults.zip file and extract the contents), and it will analyse that directory and hand over all the error details on a silver platter. Well no, not a silver platter actually, but in a nice tabular format, which you can export to an excel sheet if required. A few screenshots of how it works on the right, along with the excel outpu below. The download link is at the top. I hope a user guide is not required as I have tried to make it as intuitive as I possibly could. Adding a comments section to this page soon so you can leave feedback or questions.