Performance Testing Checklist

1. Is the interval from when a user initiates a request to the instant at which the first part of the response is received at by the application?(Response Time testing)
2. Is the total amount of work performs by the computer system over a given variation of time? (Throughput testing)
3. Does the Vusers to wait till all Vusers come to a certain point and proceed together? (Rendezvous Point testing)
4. Suddenly increasing the number of, or load generated by, users by a very large amount and observing the behavior of the system(Spike testing)

LOAD TESTING
1 Many users requesting a certain page at the same time.
2 Increase the number of users and keep the data constant
3 Does the home page load quickly? within 8 seconds
4 Is load time appropriate to content, even on a slow dial-in connection?
5 Can the site sustain long periods of usage by multiple users?
6 Can the site sustain long periods of continuous usage by 1 user?
7 Is page loading performance acceptable over modems of different speeds?
8 Does the system meet its goals for response time, throughput, and availability?
9 Have you defined standards for response time (i.e. all screens should paint within 10 seconds)?
10 Does the system operate in the same way across different computer and network configurations, platforms and environments, with different mixes of other applications?

VOLUME
1. Increase the data by having constant users
2. Will the site allow for large orders without locking out inventory if the transaction is invalid?
3. Can the site sustain large transactions without crashing?

STRESS
1. Increase both number of users and the data
2. Performance of memory, CPU, file handling etc.
3. Error in software, hardware, memory errors (leakage, overwrite or pointers)
4. Is the application or certain features going to be used only during certain periods of time or will it be used continuously 24 hours a day 7 days a week? Test that the application is able to perform during those conditions. Will downtime be allowed or is that out of the question?
5. Verify that the application is able to meet the requirements and does not run out of memory or disk space.