Load Runner Tips- Performance testing, load testing, stress testing, soak testing, endurances testing tool,VuGen script creation, Load Runner Correlation, LR Scripting, Load Runner parameterization, Load Runner transaction naming,LR think time, LR transaction, web reg save param, Web reg find, Lr pacing
 

Correlation Challenge
  1. Correlation Challenge- Beginners Level
  2. Correlation Challenge- Moderate Level
  3. Correlation Challenge- Expert Level


What is Performances Testing?
What is Load Testing? Load Testing is a process to design and simulate usage traffic which can be used to test your server for performance, reliability and scalability. Load Testing of websites involves testing the performance and scalability of your web servers with varying user load. Load testing involves simulating real-life user load for the target website. It helps you determine how your website behaves when multiple users hits it simultaneously. Load testing with different load strategies and conditions helps you determine software design issues like incorrect concurrency/pooling mechanism, poor optimization, memory build-up, etc. Load Testing helps you identify server configuration issues with Web server, application server, database server, load balancer, etc. Load Testing helps you detect if your current infrastructure is sufficient to meet your user demand. Load Testing helps you determine the peak user load your website can sustain, number of concurrent users your website can support, and whether or not your website will scale as more users access it.
Load testing will provide you answers of below questions:
• Do you know the number of concurrent users that your website can safely support?
• Will your website scale as more users access it?
• Do you know how long it would take a visitor to receive a page?
• Do you know the load point where your server crashes?
• Is your current hardware sufficient to meet your predicted demand? If no, what additional hardware would you need? Load Testing can help you identify a variety of problems before you go into production:
• Software design issues (incorrect concurrency/pooling mechanism, poor optimization, memory build-up, etc.)
• Server configuration issues (Web server, application server, database server, load balancer, etc.)
• Hardware limitation issues (Excessive disk I/O, CPU maximization, memory limitations, network bottleneck, etc.)