What is Soak Testing?

This is a non-functional testing. In the Soak Testing, the System under Load (SUL) is checked that it can face an immense/large volume of the load for an extended timeframe.

Soak Testing is only a kind of a performance test.

This testing is done at a system level, to discover whether the system will confront a high volume of use and to see what might happen outside its outline desires/expectations.

The picture above delineates testing cycle that shows at which arrange the Soak Testing (Type of Performance Test) is performed on an application. In this sort of testing, what fundamentally checked is the memory usage by an application in a system.

Why Soak Testing:-

A system may behave normally when utilized for 2 hours, however when the same system is utilized continuously for 10 hours or more than that then it might fail or act strangely/haphazardly/it might crash. To foresee such disappointment Soak Testing is performed.

When to do Soak Testing:-

Soak Testing ought to be done in taking after scenarios: -

Before the built is deployed to the customer i.e. preceding the release of any application on a particular stage, it needs to experience a successful arrangement of load tests at high or comparable traffic levels. After that soak testing is performed. It helps us to decide how to run a specific application for an extended period. Issues like memory breaks/memory corruption are found amid the period i.e. when it is on Soak, then it ought to be quickly reported.

The best time to do a soak testing is throughout the weekends as an application should be in a running state for whatever length of time that over a day or night. It totally relies on upon the limitations of the testing circumstance. Soak tests are the most important compliance requirements which should be entirely trailed by each organization.

EXAMPLES of Soak Testing:-

In the case of banking domain when there is a lot of information from vendors/merchants, the analyzer will put the system under load consistently for 70hrs to 150 hrs to check how the application behaves on amid this loading period.

Assume there are 33,000 logins, which should be put through the system, it represents to seven and a half days of activity. For this situation, We can start, soak testing of 60-70 hours from Monday 6pm and it will finish by Thursday 6am. Just with such a test, it will be conceivable to watch any corruption of performance under the controlled conditions.