Performance testing is aimed to ensure that the tested software or application works properly under critical conditions. It helps determine how quickly some specific parts of its system respond in different situations.

Therefore, it’s quite important to have requirements for performance tests and know the places where to find this information.

Overall Information

1. What’s the timeframe of the current project so you can plan the start and completion of the testing process?
2. Are there any results of functional testing? How does the application behave?
3. Some tests showed that a firewall may affect the results of load testing. Should we obtain permission from the firewall before we start testing?
4. What are the URL and credentials of the application?
5. Are there any suggestions for testing tools? – LoadRunner, JMeter, etc.
6. What type exactly performance testing should the QA engineers complete? – Stress testing, load testing, capacity testing, soak testing.
7. What are the objectives of the testing process? – find the system vulnerabilities, see the platform that performs better in comparison with another one, and assess the system by performance criteria.
8. What are the acceptance criteria for every test? – the response time of each transaction should be less than 10 sec; at least 90% of user transactions should be successful.

Architecture

1. What kind of application is it? – mobile, web, client-server.
2. What platform was used to develop the product? – PHP, Ruby, .Net, etc.
3. What’s the database? – SQL, MySQL, Oracle.
4. What application server does the system use? – WebSphere, Tomcat, IIS.
5. What’s the system hardware (with all servers, configurations, and interaction mechanisms)? – LAN/WAN, bandwidth techniques, batch transactions, terminal servers, etc.
6. Do you have a tool on a web server to monitor traffic? – Google analytics, AppDynamics, New Relic.
7. Are there any defects already found? – timeout error due to longer response time, unexpected increase in the number of visitors per some period, and higher CPU and memory usage.
8. What is the client-server protocol? – HTTP, HTTPS, TCP/IP.
9. Does the web application depend on the browser version of the client?
10. Is it possible to run tests in a separate test environment? – it is highly recommended.
11. Are there any special input requirements? – data verification, uniqueness, time sensitivity.

Business

1. Do you know already the performance scenarios? – for some social networks these can be the login process, viewing/adding posts, message exchange, etc.
2. Do you know the exact number of users who have visited the website in hours?
3. What’s the way users access the application? – from time to time during the day; simultaneous login.
4. How long do users use the application for one session?
5. What’s the number of transactions users complete per day?
6. Is the location of your users important? Is it the same place or they are worldwide?
7. What’s the way users access the application? – web, mobile, remote desktop protocol.
8. Have you set an acceptable maximum time to complete the transaction? – the system should respond within 5 seconds.
9. What are the peak load days/hours of maximum energy consumption on a server?
10. How many users visit the system during this peak load time?
11. What’s the workload model?
12. What’s the exact number of users who can access the system simultaneously?
13. Are there time limits for test performance?
14. Do you have any additional information that can help with testing?

To sum up, we’d like to emphasize one more time that the purpose of performance testing is not to find bugs but to eliminate vulnerabilities in the software performance at the stage of modeling and design of the system, before the main stage of development. Hence, it is significantly important to get ready properly for test runs and to do everything the best way.