Performance Test Plan

performance Test Plan contains....
-Project requirements:
-functional requirements
-functionality of application
e.g. Login functionality
user should be able to login into application with valid username and password.if user enters invalid username/password , application has to give an error message
-non-functional requirements
-performance requirements
-Performance of application
e.g. how much time the user took to login into application
50 concurrent users login, time < 100 sec
100 concurrent users login, time < 200 sec
Types of test:
-load test:
-testing an application with requested no. of users.         The main objective is to check whether application can         sustain the no. of users with the time frame.
50 concurrent users login, time < 100 sec
100 concurrent users login, time < 200 sec
no. of users (vs) response time
    -stress test:
-testing an application with requested no. of users  over a time period. The main objective is to check             stability/reliability of application
-Capacity test:
-to check max. user load. How many users the application can sustain.
ramp up scenario
Components in loadrunner:
-virtual user generator
-Create ONE virtual user (vUser: simulation of real         user)
-record script
-enhancements:
-parametrization:
-test with more data sets
-check points
-to verify expected result
-correlation(regular expressions)
-to handle dynamic objects
-controller
-controller
-how many such users you need e.g. 50
-design load test scenario
-manual scenario
-no. of users (vs) response time
-no. of users is defined
-goal oriented scenario
-define a goal
- 20 hits per sec
- 10 transactions per sec
-run test scenario
-monitor test scenario
-generate dynamic graphs
-analysis
-prepare load test reports
-send it to project stake holders

example:
Load Performance Test

No comments: