Performance Testing Interview Questions You Need to Master in 2019

Performance Testing is a type of software testing which ensures that the application is performing well under the workload. The goal of performance testing is not to find bugs but to eliminate performance bottlenecks. It measures the quality attributes of the system.

The attributes of Performance Testing include:
Speed – It determines whether the application responds quickly.
Scalability – It determines maximum user load the software application can handle.
Stability – It determines if the application is stable under varying loads.

Load testing – It checks the application’s ability to perform under anticipated user loads. The objective is to identify performance bottlenecks before the software application goes live.
Stress testing – This involves testing an application under extreme workloads to see how it handles high traffic or data processing. The objective is to identify the breaking point of an application.
Endurance testing – It is done to make sure the software can handle the expected load over a long period of time.
Spike testing – This tests the software’s reaction to sudden large spikes in the load generated by users.
Volume testing – Under Volume Testing large no. of. Data is populated in a database and the overall software system’s behavior is monitored.
Scalability testing – The objective of scalability testing is to determine the software application’s effectiveness in scaling up to support an increase in user load.

Some of the common performance problems faced by users are:
Longer loading time
Poor response time
Poor Scalability
Bottlenecking such as coding errors or hardware issues

The market is full of a number of tools for test management, performance testing, GUI testing, functional testing, etc. I would suggest you opt for a tool which is on-demand, easy to learn as per your skills, generic and effective for the required type of testing. Some of the common Performance Testing tools are:
LoadView
Apache JMeter
LoadUI Pro
WebLoad
NeoLoad

The Parameters for Performance Testing are:
Memory usage
Processor usage
Bandwidth
Memory pages
Network output queue length
Response time
CPU interruption per second
Committed memory
Thread counts
Top waits

Versatility
Test Results
Easy Integrations
Robust reports
Enterprise Package

Endurance Testing – It is a 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 a type of performance testing that is performed to analyze the behavior of the system when the load is increased substantially.

The common mistakes done in Performance Testing are:
Direct jump to multi-user tests
Test results not validated
Unknown workload details
Too small run duration
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

Performance tuning is the improvement of system performance. Typically in computer systems, the motivation for such activity is called a performance problem. It can be either real or anticipated and most systems will respond to increased load with some degree of decreasing performance.

There are two types of Performance Tuning:
Hardware Tuning – Enhancing, adding or supplanting the hardware components of the system under test and changes in the framework level to augment the system’s 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.

To continue reading more questions, you can click here