You are on page 1of 2

LOAD TESTING is done to identify the maximum operatoing capacity of aplication a nd also to identify the bottleneck that interfere

while operating at that capaci ty (maximum) Roles and Responsibilities: ***************************** 1) review the test plan and check if i have all details to start proceeding with : a) Defining the test cases b)Creating the script c)Validate the script d)Configure the test scenario e) execute the test f) Monitor the test g) Analyse the result to an extent LOAD RUNNER consists of: 1) VuGEN - Virtual User Generator 2) CONTROLLER - Designs and runs the scenario. 3) ANALYSIS - Analyzes the scenario BEFORE TEST PLANNING: ********************************* 1) Pre-release the check list. 2) Review the high level design for upcoming functionalities. 3)Review the performance critical scenarios 4)Attendindg demo for new functionalities and understand the performance impact from those functionalities. 5)Review the test stratergy HOW TO DO WORK LOAD SCENARIO: *********************************************** Consider a shopping site for shich we are doing the work load scenario. Follow t he below steps: 1) Try to understand the peak day of the week i.e (day on which the site is full y busy) eg: WEDNESDAY 2) Then understand the peak time in that day (conitnous 2 or 3 hours) eg: 6 AM t o 8 AM 3)Find out what are the transaction which took place during those hours. (For th is we shoule be fully clear with business transactions ) Typically for a shopping site, the business transactions can be: LOGIN, SEARC H, VIEW PRODUCT CATALOGUE, CHECK OUT ITEM, LOG OUT etc 4)Find out the usage rate of these business transactions Eg: Between 6 AM to 8 AM, if the total no of server calls are 10,0000. Out of that, find out how many calls were made for LOGIN, SEARCH, VIEW PRODUCT CATALOGUE, CHECK OUT ITEM, LOG OUT If any of the above busniness transaction accounts for more than or equal to 2 % of total transactions (10,0000), those buniess transaction has to conside red for perfromance testing. The above details can be obtained from sitescope or google analytics WORKLOAD DEFINITION

7)Recommodation and various links for graphs of each utilization . 5) Use the tools (Loa runner or JMeter or OPENSTA) to implement the load and cap ture the metrics 6) Analyse those metrics TEST REPORT: ****************** 1) Objective of each test. (Data retieval from DB and data storing into the DB) c) Revenue Generating business transaction (which transaction in the ap plication generates money for the company) 2) Identify the work load model to distribute the entire load for the above crit ical scenarios 3)Identify the metrics(what to be measured). sear ch page. 6)Risks(if any) before production. 2) Executive summary of each test 3)Stake holder and reviewer's details 4) CPU.e a) Max no of users using that business transaction (eg: login page.memory. THROUGHPUT and HITS/SECONDS graphs 5) Comparison of transaction response time with previous result.OS ? 3) what is the webserver and DB server? 3) how does my webserver communicate with app client? i. 4)Design the test to simulate the load.e what protocol to be us ed? 4) what is the middle config and app server between my client and back-end serve r? 5) what are the network component that will affect the response time? 6) what are the throughput of my communication devices? TO DO LOAD TEST: *********************** 1) Identify the performnace critical scenarios i. that we want to verify against the performance objective.****************************** 1) no of users anticipated to connect to my system? 2) app client's config: hardware. checkout page etc for shopping site) b) Maximum amount of data used.