Dhiren Patel

05/18/2011

Assignment 2

Core performance Testing Activities

Requirement collection

Plan & Design Test

Script

Run

Analyze

Report

Dhiren Patel

05/18/2011

Core Performance Testing Activities 1. Requirement Collection:Identify the physical test environment and the production environment as well as the tools and resources available for the test. The physical environment includes hardware, software, and network configurations. Having a thorough understanding of the entire test environment at this level help to plan the whole test. Main components need to remember while collecting requirements: a) Infrastructural differences: Need to collect final design layout from architecture so when there is any changes made in the system must satisfy that Infrastructure. b) Identify most critical transactions: Identify which is most critical parameter need to consider while testing. Parameter likes security, response time, load, etc Example:- if the software made for banking than security will be most critical transaction, If software made for selling items online than credit card payment option will be most critical transaction, If its for social networking or email than number of user (load) will be most critical transaction. c) Accepted response time: Response time must be satisfied the customer requirements and application needs. If it takes long time to operate function, which is most crucial part of the software company will lose the customers. No one like to wait too long for operate few functions. Identify the accepted response time so we can run the test based on that requirement. Without knowing any base response time we cannot run the test correctly.

Dhiren Patel

05/18/2011

d) Load rates Identify the load rates based on this two conditions (A) concurrent users: Gather data on how many users will use this application and based on that count the number of user for a particular time period so we can conduct the test based on that load. Example: - if you consider the bar and there are 2000 people visit in one month than there will be average 66 people come in one day. Which are consider as concurrent users and load will count for one day is 66. (B) No. of people at a time: This load consider based on how many user use the application at a same time. Example: - If we take the same example as above for this case load will count based on number of people waiting at the counter for drink. Because in actual case all 66 people will not drink whole day and all the time so the load will be vary every hours. e) Peak load : It is a load when the maximum number of users will use the application at same time Example: If we use the same example of bar there is a average daily load is 66 people but on Friday and Saturday there must be more than the average people go for drink which is called peak load which will be a maximum number of people visit that bar respected to other days. 2. Plan and Design Test: Identify the response time, throughput, and resource utilization goals and constraints. In general, response time is a user concern, throughput is a business concern, and resource utilization is a system concern.

Dhiren Patel

05/18/2011

Identify key scenarios, determine variability among representative users and how to simulate that variability, define test data, and establish metrics to be collected. Consolidate this information into one or more models of system usage to be implemented, executed, and analyzed. Prepare the test environment, tools, and resources necessary to execute each strategy as features and components become available for test. Develop the performance tests in accordance with the test design. 3. Script: By using VuGen (Virtual user Generator) create script. 4. Run: Run script in controller to test performance of the software at different level by considering all gathered data. (As per step 1) Run and monitor the test. Validate the tests, test data, and results collection. Execute validated tests for analysis while monitoring the test and the test environment. 5. Analyze: Consolidate and share results data. Analyze the test data both individually and as a cross functional team. 6. Report: When analysis is done check all metrics values comes within accepted limits or not and make a report. Report includes test is finish under particular scenario on that particular configuration. If any of the set thresholds violated then send back to developer to fix the errors.