Load testing process
Explain the load testing process?
Step1: Planning the test:
Here, we develop a clearly defined test plan to ensure the test scenarios we develop will accomplish load testing objectives.
Step2: Creating V-users:
Here, we create Vuser scripts that contain tasks performed by each Vusers, tasks performed by Vusers as whole, and tasks measured as transactions.
Step3: Creating the scenario:
A scenario describes the events that occurred during the testing session.It includes a list of machines scripts and Vusers that run during the scenario. We create scenarios using load runner controller. We can create manual scenarios as well as goal oriented scenarios. In manual scenarios, we defined the number of Vusers, the load generated machines, and percentage of Vusers to be assigned to each script. For web tests we may create a goal oriented scenario where we define the goal that our test has to achieve. Load runner automatically builds a scenarios for us.
Step4: Running the Scenario:
We emulate load on the server by instructing multiple Vusers to perform tasks simultaneously. Before the testing, we set the scenario configuration and scheduling. We can run the entire scenario, Vuser groups, or individual Vusers.
Step5: Monitoring the scenario:
We monitor scenario execution using the load runner online run time transaction system resource, web resource, web server resource, web application server resource, database server resource, network delay, streaming media resource, firewall server resource, ERP server resource and Java performance monitors.
Step6: Analyzing the Test results:
During the scenario execution LR records the performance of the application under different loads. We use load runner?s graphs and reports to analyze the application performance.