Product or Application Stress Testing
–The application or product stress testing is mainly focused on determining the faults related to network issues, data locking, blocking, and a performance bottleneck in a software product.
Server-client or Distribute Stress Testing
–In this type of stress testing, all the clients related to the server are tested.
–The distribute stress testing is used to perform across all clients from the server.
Analytical/ Exploratory Stress Testing
–Analytical or exploratory testing is used to execute the system with unusual constraints unlikely to occur in a real scenario.
–It is mainly used to identify the bugs in rare situations such as a large number of users logged simultaneously or a database went offline when retrieved from a website.
Let see some examples of analytical Stress Testing where such irregular conditions are used:
–When a large number of parallel users try to log into the application.
–Data is added in enormously large quantity in the database.
–When the website tries to reach it from the front end, and database linked to the website shuts down.
Systematic Stress Testing
–It is combined testing used to execute the test across various systems running on a similar server.
–Using systematic stress testing, we can easily detect the bottleneck where data of one application blocks another application.
Transactional Stress Testing
–Another type of stress testing is transactional stress testing, which is used to implemented one or more transactions between various applications.
–The main objective of performing the transactional stress testing is to enhance the system performance.