In performance testing, throughput is referred to the amount of data transported to the server in response 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.
Performance Testing Interview Questions
5) What are the sub-genres of the performance test?
Load testing: The performance testing that is done in order to examine applications performance that is based on a load that is specified and expected is termed as Load testing. The increment of load can be done by increasing the quantity of user who is performing a specified work within a specified time limit.
Volume testing: This test is performed in order to find the quantity of data that can be handled effectively and efficiently by a system.
Stress testing: this test is performed in order to make an evaluation of the performance of the system by increasing the number of users than the requirements. This is done in order to check at which level the application might crash.
Spike testing: This test is used to sterling what will happen if suddenly there is a huge increase or decrease in the number of users of the application system.
Soak testing: When there is a great deal of load for a long time on the application system then soak testing is performed to determine the behavior of the application in terms of response time and stability.
In order to make improvements in the performance of the system performance tuning is used and there are two types.
Hardware tuning: To replace, add or optimize components of hardware of the application system this kind of tuning is utilized. And also to make improvements in the performance of the system, changes are done with the help of hardware tuning on the level of infrastructure.
Software tuning: This tuning is helpful when it comes to identifying the bottlenecks of a software level. These identifications are done with the help of profiling the database and code. With the help of this tuning, modifications are made to the software in order to rectify the bottlenecks.
42) What is Soak testing in performance testing?
Expecting a continual increase in the load, system resources are monitored with their performances getting affected with load increase. In the due course of the time any data leak is monitored and the memory management is observed to make sure, performance does not affect any of the memory constraints and no data loss happens.
Performance Testing Interview Questions
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.
Longer loading time
Poor response time
Poor Scalability
Bottlenecking such as coding errors or hardware issues
LoadView
Apache JMeter
LoadUI Pro
WebLoad
NeoLoad
CPU Utilization
Memory Utilization
Networking Utilization
S limitation
Disk Usage
Memory usage
Processor usage
Bandwidth
Memory pages
Network output queue length
Response time
CPU interruption per second
Committed memory
Thread counts
Top waits
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
Performance Testing
Functional Testing
To validate the behavior of the system at various load conditions performance testing is done.
It gives the best result if automated
Several user performs desired operations
Customer, Tester, Developer, DBA and N/W management team
Requires close to production test environment and several H/W facilities to populate the load
To verify the accuracy of the software with definite inputs against expected output, functional testing is done.
This testing can be done manually or automated
One user performs all the operations
Customer, Tester and Development involvement is required
Production sized test environment is not necessary, and H/W requirements are minimal
Versatility
Test Results
Easy Integrations
Robust reports
Enterprise Package
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
Design or Planning
Build
Execution
Analyzing & Tuning
Benchmark Testing
Baseline Testing
It is the method of comparing performance of your system performance against an industry standard that is set by other organization
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
HTTP
HTTPS
FTP
Web Services
Citrix
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.
Q19. List the need for opting for Performance Testing.
The response time of application for the intended number of users-
Utmost load resisting capacity of an application.
The capability of the app under test to handle the particular number of transactions.
The constancy of an application under the usual and unexpected user load.
Making sure that users have an appropriate response time on production.
Complicated procedure to measure the performance of the application precisely.
Complex synchronization procedures between the two or more users.
Difficult to assess and recognize the outcomes & bottlenecks.
Increased the overall infrastructure cost.
Q21. What is Profiling in Performance Testing?
Requirement gathering
Tool selection
Performance test plan
Performance test development
Performance test modeling
Test Execution
Analysis
Report
VUGen– Records Vuser scripts that emulate the actions of real users.
Controller – Administrative center for creating, maintaining and executing load test scenarios.
Load Generator – An agent through which we can generate load.
Analysis – Provides graphs and reports that summarize the system performance
Q29. What is a correlation?
Neo load is a type of load testing tool. It measures performance of the web or mobile application. It also provides programmatic solutions to the developers to help them optimize the performance before the application goes into the production. It is available in French and English as well.
Text Check– This checks for a text/string on the web page
Check– This checks for an on a web page.
Q34. How to identify performance testing use cases for any application?There are certain measures that you need to consider while monitoring the performance tests. Users have to be working on the core functionality of the application, trying to perform operations on database like CRUD, and the number of users trying to concurrently access the application should be more. With all these criteria, even manual test cases can help you in identifying the performance measurements.
