Introduction to Performance Testing
Performance testing has the success of a business. The poor performing site faces financial losses legal repercussions at times. slow performing, an unreliable site in cases of purchasing, online test taking, bill payment. the internet being available, the alternates are immense. It is easier to lose gain them and performance is a key game changer.
Types of performance testing
The execution testing is no longer namesake checkpoint before going live. It indeed a comprehensive and detailed stage. that determine the performance of a site or application meets
The purpose of this test is the performance of the application under load, particularly users.
Load testing is a type of performance test. the application is tested for its performance on normal and peak usage. The execution of an application checked in its reaction to the client ask. its ability to respond within accepted tolerance on different user loads.
The key considerations are:
What is the max load the application is able to hold before the application starts behaving?
What amount of information is the Database ready to deal with the framework or the crash watched?
Are there any network related issue addressed?
Stress testing is the test to find the ways to break the system. The test also gives the idea for the largest load the system can hold.
Generally, Stress testing has an incremental approach where the load is increased. The test started with the good load for which application has been already tested. Then more load added to stress the system. the point starts seeing servers not responding requests considered as a breakpoint.
During this test, all the functionality of the application tested under heavy load. The back-end usefulness may run complex questions, dealing with information.
The following questions addressed:
What is the max load a system can sustain before it breaks down?
How is the system break down?
Is the system able to recover once it’s crashed?
In how many ways system can break and which are the weak node while handling the unexpected load?
Volume test confirms the execution of the application is not the volume of information. that is being handled by the application. Hence to execute Volume Test generally the huge volume of data entered into the database. This test can be an incremental or steady test. In the incremental test volume of data increased.
the application usage database size grows. It is important to test the application against the overwhelming Database.
The most common recommendation for this test is the tuning of DB queries. which access the Database for data. the response of DB queries is high for the big database. so it needs to be rewritten in a different way or index, joints included.
The capable of meeting business volume under both normal and peak load conditions?
Capacity testing is generally done for future prospects.
Capacity testing addresses the following:
Will the application able to support the future load?
Is the environment capable of standing for the upcoming increased load?
The extra resources required to make environment capable enough?
Limit testing used to decide clients and additionally exchanges a web application. It supports and still meets performance testing resources. processor capacity, network bandwidth, memory usage, disk capacity meet the goal.
Online Banking is a perfect example of where capacity testing could play a major part.
It verifies the application is able to return back to its normal state. It not after a failure or abnormal behavior long does it take for it to do so.
An online trading site if experience a failure. where the users are not able to buy/sell shares at a certain point of the day. In this case, we can say the application is reliable or recovered from the abnormal behavior.