Friday, 14 August 2015

MT - 54 - SOAK/Endurance Testing !

Also known as endurance testing , soak testing is done to see the behaviour of the system after giving load for a prolonged period of time.Soak Testing is the form of Performance Testing, which incorporate testing a system with expressive load extended over an expressive period of time, to discover how the system and product behaves under repeated use.

As an example we can take the closing of the banks that are done at the end of year. At this time there is a huge load on the server for a prolonged period of time. At this time we would not want the application to crash or show slow response time, so endurance testing is done.

 A soak test would generally execute some times more transactions in an entire (full) day (or night) that intend be expected in a busy day, to distinguish any performance issues that appear after a immense number of transactions have been executed.A soak test also called an endurance test is generally done to originate whether an application can handle with the continuous expected load. A soak test is also used to audit whether there is any performance degradation afterwards a long period of activity.The goal is to discover how the system behaves under sustained use. That is, to ensure that the throughput and/or response times after some long period of sustained activity are as good or better than at the beginning of the test.It may also be used to check memory leaks and failure of the application over a long period of time.

No comments:

Post a Comment