Performance testing interview questions and answers

Q1. Why Performance Testing is performed? Performance Testing is performed to evaluate application performance under some load and stress condition. It is generally measured in terms of response time for the user activity. It is designed to test the whole performance of the system at high load and stress condition. Example: Customer like to withdraw money from an ATM counter, customer inserts debit or credit card and wait for the response. If system takes more than 5 min. then according to requirements system functioning is fail. Type of Performance Testing: Load: analogous to volume testing and determine how application deal with large amount of data. Stress: examine application behavior under peak bursts of activity. Capacity: measure overall capacity and determine at what time response time become unacceptable. Q2. What are tools of performance testing? Following are some popular commercial testing tools are: LoadRunner(HP): this for web and other application. It provides a variety of application environments, platforms and database. Number of server monitors to evaluate the performance measurement of each component and tracking of bottlenecks. QAload(Compuware): used for load testing of web, database and char-based system. WebLoad(RadView): it allows comparing of running test vs. test metrics. Rational Performance Tester (IBM): used to identify presence and cause of system performance bottlenecks. Silk Performer (Borland): allow prediction of behavior of e-business environment before it is deployed, regardless of size and complexity. Q3. Explain the sub-genres of Performance testing. Following are the sub-genres of Performance Testing: Load Testing: it is conducted to examine the performance of application for a specific expected load. Load can be increased by increasing the number of user performing a specific task on the application in a specific time period. Stress Testing: is conducted to evaluate a system performance by increasing the number of user more than the limits of its specified requirements. It is performed to understand at which level application crash. Volume Testing: test an application in order to determine how much amount of data it can handle efficiently and effectively. Spike Testing: what changes happens on the application when suddenly large number of user increased or decreased. Soak Testing: is performed to understand the application behavior when we apply load for a long period of time what happens on the stability and response time of application. Q4.What is performance tuning? To improve the system performance we follow a mechanism, known as Performance tuning. To improve the systems performance there are two types of tuning performed: Hardware tuning: Optimizing, adding or replacing the hardware components of the system and changes in the infrastructure level to improve the systems performance is called hardware tuning. Software tuning: Identifying the software level bottlenecks by profiling the code, database etc. Fine tuning or modifying the software to fix the bottlenecks is called software tuning. Q5. What is concurrent user hits in load testing? When the multiple users, without any time difference, hits on a same event of the application under the load test is called a concurrent user hit. The concurrency point is added so that multiple Virtual User can work on a single event of the application. By adding concurrency point, the virtual users will wait for the other Virtual users which are running the scripts, if they reach early. When all the users reached to the concurrency point, only then they start hitting the requests. Q6. What is the need for Performance testing? Performance testing is needed to verify the below: Response time of application for the intended number of users Maximum load resisting capacity of application. Capacity of application to handling the number of transactions. Stability of application under expected and unexpected user load. Ensuring that users have proper response time on production Q7. What is the reason behind performing automated load testing? Following drawbacks of manual Load Testing that leads to Automation load testing: Difficult to measure the performance of the application accurately. Difficult to do synchronization between the users. Number of real time users are required to involve in Performance Testing Difficult to analyze and identify the results & bottlenecks. Increases the infrastructure cost Q8. What are the exiting and entering criteria in the performance testing? We can start the performance testing of application during the design. After the execution of the performance testing, we collected the results and analyzed them to improve the performance. The performance tuning processed will be performed throughout the application development life cycle. Performance tuning is performed which is based on factors like release time of application and user requirements of application stability, reliability and scalability under load, stress and performance tolerance criteria. In some projects the end criteria is defined based on the client performance requirements defined for each section of the application. When product reaches to the expected level then that can be considered as the end criteria for performance testing. Q9.How do you identify the performance bottlenecks situations? Performance Bottlenecks can identify by monitoring the application against load and stress condition. To find bottleneck situation in performance testing we use Load Runner because provides different types of monitors like run-time monitor, web resource monitor, network delay monitor, firewall monitor, database server monitor, ERP server resources monitor and Java performance monitor. These monitors can help to us to determine the condition which causes increased response time of the application. The measurements of performance of the application are based on response time, throughput, hits per sec, network delay graphs, etc. Q10. What activities are performed during performance testing of any application? Following activities are performed during testing of application: 1. Create user scenarios 2. User Distribution 3. Scripting 4. Dry run of the application 5. Running load test and analyzing the result., Q11. How can we perform spike testing in JMeter? Spike Testing is performed to understand what changes happens on the application when suddenly large number of user increased or decreased. Sudden changes in the number of user by increasing or decreasing at certain point of application and then monitoring the behavior. In JMeter spike testing can be achieved using Synchronizing Timer. The threads are blocked by synchronizing the timer until a particular number of threads have been blocked, and then release them at once thus creating large instantaneous load. Q12. What is distributed load testing? Distributed load testing: in this we test the application for a number of users accessing the application at a same time. In distributed load testing test cases are execute to determine the application behavior. Now application behavior is monitored, recorded and analyzed when multiple users concurrently use the system. Distributed load testing is the process using which multiple systems can be used for simulating load of large number of users. The reason for doing the distributed load testing is that to overcome the limitation single system to generate large number of threads. Q13. Explain the basic requirements of Performance test plan. Any Software Performance Test Plan should have the minimum contents as mentioned below: Performance Test Strategy and scope definitions. Test process and methodologies. Test tool details. Test cases details including scripting and script maintenance mechanisms. Resource allocations and responsibilities for Testers. Risk management definitions. Test Start /Stop criteria along with Pass/Fail criteria definitions. Test environment setup requirements. Virtual Users, Load, Volume Load Definitions for Different Performance Test Phases. Results Analysis and Reporting format definitions Q14. What is throughput in Performance Testing? Throughput in Performance testing is the amount of data sent by the server in responds to the client request in a given period of time or it is the number of units of work that can be handled per unit of time. The throughput is measured in terms of requests per second, calls per day, hits per second, reports per year, etc. In most of the cases, the throughput is calculated in bits per seconds. Higher the throughput value, higher the performance of the application It is includes the client side statistics. Q15. What are the automated Performance testing phases? The phases involved in automated performance testing are: Planning/Design: This is the primary phase where team will be gathering the requirements of the performance testing. Requirements can be Business, Technical, System and Team requirements. Build: This phase consists of automating the requirements collected during the design phase. Execution: it is done in multiple phases. It consists of various types of testing like baseline, benchmarking testing Analyzing and tuning: During the performance testing we will be capturing all the details related to the system like Response time and System Resources for identifying the major bottlenecks of the system. After the bottlenecks are identified we have to tune the system to improve the overall performance. Q16. What is Performance Testing? Performance Testing is performed to determine response time of the some components of the system perform under a particular workload. It is generally measured in terms of response time for the user activity. It is designed to test the overall performance of the system at high load and stress condition It identifies the drawback of the architectural design which helps to tune the application. It includes the following: Increasing number of users interacting with the system. Determine the Response time. Repeating the load consistently. Monitoring the system components under controlled load. Providing robust analysis and reporting engines. Q17. What is baseline testing? Baseline testing is a testing which is performed on the application before coming to any conclusion. It can be either the verification or validation process which provides an idea of what the next stage has to do. It is very important testing technique, if done properly, 85% of performance problems can be identified and solved when proper baseline tests are done. Q18. What is the testing lifecycle? There is no standard testing life cycle, but it is consist of following phases: Test Planning (Test Strategy, Test Plan, Test Bed Creation) Test Development (Test Procedures, Test Scenarios, Test Cases) Test Execution Result Analysis (compare Expected to Actual results) Defect Tracking Reporting Q19. What is the difference between baseline and benchmark testing? The differences between baseline and benchmark testing are: Baseline testing is the process of running a set of tests to capture performance information. This information can be used as a point of reference when in future changes are made to the application where as Benchmarking is the process of comparing your system performance against an industry standard that is given by some other organization. Example: We can run baseline test of an application, collect and analyze results, and then modify several indexes on a SQL Server database and run the same test again, using the previous results to determine whether or not the new results were better, worse, or about the same.