I'm Vijay, and I've been working on this blog for the past 20+ years! I’ve been in the IT industry for more than 20 years now. I completed my graduation in B.E. Computer Science from a reputed Pune university and then started my career in…
Here, in this informative tutorial, we will explore all about Test Result Analysis and Reports in LoadRunner in simple terms along with a video tutorial for your clear understanding.
#1. Analysis is the utility to analyses the LoadRunner results.
#2. LoadRunner results are saved in .lrr file and can be viewed using Analysis.
#3. Analysis gathers the result information from scenario results (lrr file) and stores the information in form of .lra file.
#4. LoadRunner result has “Log” folder which contains Vuser logs and saves snapshots on error.
#5. Analysis generates Analysis Summary for the test which gives good idea about the test.
#6. Analysis generates graphs from the data collected during the test execution.
#7. Few of the graphs which are important for analysis of the results are Running Vusers, Hit per second, Throughput, Transaction Summary, Average Transaction Response Time, Error per second, etc.
#8. Analysis provides the raw data from which graphs are created.
#9. The granularity of graph should be such that it has maximized readability along with accurately represent important events.
#10. Analysis also provides facility to compare the results for the test.
#11. Analysis has good reporting mechanism which is helpful in sharing the test results.
#12. In Analysis, customized templates can be created to generate the same report for other test results.
#13. LoadRunner provides many formats to save the report.
All That You Need to Know about Correlation in LoadRunner: Parameterization in LoadRunner was explained in detail in our previous tutorial. Here, in this tutorial, we will explore the concept of Correlation in LoadRunner in detail in simple terms along with a classic video tutorial for your reference. => Click Here…
HP LoadRunner is now changed to Micro Focus LoadRunner but still, the content on the page is valid on the new Micro Focus domain and tools as well. This introductory tutorial will explain to you all about Micro Focus LoadRunner in detail along with a video tutorial for your easy…
What is LoadUI? LoadUI is a free and open-source load testing tool that allows you to perform complex load tests and test performance by simply dragging different components around. LoadUI lets you create and update test cases while you run them. What makes load UI powerful is the focus on…
Difference Between Performance Testing, Load Testing, and Stress Testing – With Examples Our previous tutorial in this series will be the best Performance Testing Guide for any beginner. In the software testing field, we come across terms like performance testing, load testing, stress testing, etc. These terms are often misunderstood…
LoadRunner Tutorials: Hands-on free training course for beginners (and helpful for experienced professionals as well!) Micro Focus LoadRunner (earlier HP) is one of the most popular load testing software. It is used to performance test an application under the load. It can simulate thousands of concurrent users to produce real-time load…
Web Service Scripting using the Web Services Protocol in LoadRunner VuGen: In this LoadRunner Training Tutorials for Beginners, we learned more about LoadRunner Functions. This tutorial is an addendum to our VuGen scripting series, here we will learn to script in one of the most important protocols (other than Web-HTTP/HTML…
What is Cloud Performance Testing and What are the Top Cloud-Based Performance Testing Service Providers? In the last tutorial, we came across the Ways to Supercharge your Performance Testing in detail. With the emergence of Cloud Technology, all of us are now moving towards adopting a cloud-based paradigm and this is…
What is Monkey Testing in Software Testing? Introduction: Monkey testing is a technique in software testing where the user tests the application by providing random inputs and checking the behavior (or trying to crash the application). Mostly this technique is done automatically where the user enters any random invalid inputs…