Top 20 Performance Testing-Interview Questions

Q1. Explain what is performance testing?

Ans: Performance testing is done for quality assurance. It involves testing software application to make sure that the software is working well under their expected workload.

Q2. Mention different types of performance testing?

Ans:

• Load testing
• Stress testing
• Endurance testing
• Spike testing
• Volume testing
• Scalability testing

Q3. List out what are the common performance problem does user face?

Ans:

• Longer loading time
• Poor response time
• Poor Scalability
• Bottlenecking (coding errors or hardware issues)

Q4. List out some common performance bottlenecks?

Ans: Some common performance bottlenecks include

• CPU Utilization
• Memory Utilization
• Networking Utilization
• S limitation
• Disk Usage

Q5. List out some of the performance testing tool?

Ans:

• HP Loader
• HTTP Load
• Proxy Sniffer
• Rational Performance Tester
• JMeter
• Borland Silk Performer

Q6. Why does JMeter become a natural choice of tester when it comes to performance testing?

Ans: JMeter tool has benefits like

• It can be used for testing both static resources like HTML and JavaScript, as well as dynamic resources like Servlets, Ajax, JSP, etc.
• JMeter has a tendency to determine the maximum number of concurrent users that your website can handle
• It provides a variety of graphical analyses of performance reports

Q7. Mention what all thing involves in Performance Testing Process?

Ans:

• Right testing environment:Figure out the physical test environment before carry performance testing, like hardware, software and network configuration
• Identify the performance acceptance criteria: It contains constraints and goals for throughput, response times and resource allocation
• Plan and design Performance tests:Define how usage is likely to vary among end users, and find key scenarios to test for all possible use cases
• Test environment configuration: Before the execution, prepare the testing environment and arranges tools, other resources, etc.
• Test design implementation: According to your test design, create a performance test
• Run the tests: Execute and monitor the tests
• Analyze, tune and retest: Analyze, consolidate and share test results. After that, fine tune and test again to see if there is any enhancement in performance. Stop the test, if CPU is causing bottlenecking.

Q8. List out some of the parameters considered for performance testing?

Ans:

• Memory usage
• Processor usage
• Bandwidth
• Memory pages
• Network output queue length
• Response time
• CPU interruption per second
• Committed memory
• Thread counts
• Top waits, etc.

Q9. List out the factors you must consider before selecting performance tools?

Ans:

• Customer preference tool
• Availability of license within customer machine
• Availability of test environment
• Additional protocol support
• License cost
• Efficiency of tool
• User options for testing
• Vendor support

Q10. Mention what is the difference between JMeter and SOAPUI?

Ans:

Q11. Mention what is the difference between performance testing and functional testing?

Ans:

Q12. Mention what is the benefit of LoadRunner on testing tools?

Ans: Benefit of LoadRunner testing tools is

• Versatility
• Test Results
• Easy Integrations
• Robust reports
• Enterprise Package

Q13. Explain what is Endurance Testing and Spike Testing?

Ans:

• Endurance Testing: It is one type of performance testing where the testing is conducted to evaluate the behavior of the system when a significant workload is given continuously
• Spike Testing: It is also a type of performance testing that is performed to analyze the behavior of the system when the load is increased substantially.

Q14. Explain what are the common mistakes done in Performance Testing?

Ans: The common mistakes done in Performance Testing are

• Direct jump to multi-user tests
• Test results not validated
• Unknown workload details
• Too small run durations
• Lacking long duration sustainability test
• Confusion on definition of concurrent users
• Data not populated sufficiently
• Significant difference between test and production environment
• Network bandwidth not simulated
• Underestimating performance testing schedules
• Incorrect extrapolation of pilots
• Inappropriate base-lining of configurations

Q15. Mention the steps required in JMeter to create a performance test plan?

Ans: To create a performance test plan in JMeter

• Add thread group
• Add JMeter elements
• Add Graph result
• Run test & get the result

Q16. Explain how you can execute spike testing in JMeter?

Ans: In JMeter, spike testing can be done by using Synchronizing Timer.  The threads are jammed by synchronizing the timer until a specific number of threads have been blocked and then release at once, creating a large instantaneous load.

Q17. Explain what is the throughput in Performance Testing?

Ans: In performance testing, throughput is referred to the amount of data transported to the server in responds to the client request at a given period of time. It is calculated in terms of requests per second, calls per day, reports per year, hits per second, etc. Performance of application depends on throughput value, higher the value of throughput -higher the performance of the application.

Q18. Mention what are the phases for automated performance testing?

Ans: Phases for automated performance testing includes

• Design or Planning
• Build
• Execution
• Analyzing & Tuning

Q19. Mention what is the difference between the benchmark testing and baseline testing?

Ans:

• Benchmark Testing:It is the method of comparing performance of your system performance against an industry standard that is set by other organization
• Baseline Testing:It is the procedure of running a set of tests to capture performance information. When future change is made in the application, this information is used as a reference

Q20. Mention what is concurrent user hits in load testing?

Ans: In load testing, without any time difference when multiple users hit on the same event of an application under the load test is called a concurrent user hit.