This document deals with the checklist to be followed on course of Performance testing an application. This checklist contains the common points and cannot be decided complete as there might be more processes involved in different applications.
Checklist for defining steps of a comprehensive Performance Testing process
- List all testing milestones and deliverables for every phase of the project.
- Create a comprehensive production physical architecture diagram that shows a very low level of detail, including how each component will be connected
- List all hardware and software requirements for the tests.
- Determine all database data volume requirements
- Define all performance objectives
- Identify all performance benchmarks, if available
- Identify the total number of expected users
- Specify the minimum and maximum number of concurrent users.
- Select business scenarios (manual scripts), plus actions with each scenario that should be measured
- Determine the user load mix.
- Define Acceptable Average Response times per transaction
- Define the average hits/second or number of transactions per day
- Define the peak hour load for each scenario
- Define throughput, if applicable
- Identify any concurrent batch processes that are running
- Identify all lead, technical, functional, support and environment contact personnel.
- Compare the testing environment with the proposed environment.
- Identify whether desired load could be attained with the current environment setup
- Ensure all the components are installed and working in the testing environment
- Pipe-clean scenario executions to ensure the component states
- Identify the Load generator tool to be used, if any
- Prepare load generator scripts for each business scenario (can be manual or recorded, depending upon the tool)
- Prepare scenarios using the tool defining the transaction mix among business transactions, scheduling of iterations and setting up of the virtual users
- Identify the analysis/report contents
- Identify the components to be monitored
- Identify monitoring tools to be used, if any
- Identify log processing mechanisms if dealing with asynchronous responses such as B2B applications
- Prepare the code to process logs from each component
Define method of correlating log processing across components such as analysis graphs
