Endurance testing is a non-functional sort of software testing in which a software is tested under heavy load for a long period of time in order to assess how the software will behave when used continuously. The main goal of endurance testing is to make sure the application can manage increased load without seeing any degradation in response time.
The performance run cycle’s final phase includes this kind of testing. The procedure of endurance testing can sometimes take up to a year. This can entail adding external loads like Internet traffic or user activity. Because of this, endurance testing is distinct from load testing, which typically has an hour or so to run its course.
GOALS OF ENDURANCE TESTING
-Endurance testing’s main objective is to look for memory leaks.
-To learn how the technology works when it is used continuously.
-To guarantee that the system’s reaction time will be the same as at test’s beginning or better after a considerable amount of time.
-Figuring out how many users and/or transactions a particular system can handle while still performing well.
-Understanding how much extra resources (such as CPU power, disc space, memory use, or network bandwidth) are required to sustain utilisation in the future is crucial for managing the anticipated loads.
-In order to test a system’s endurance, it is often either overloaded or given fewer resources, with the results being evaluated.
-It is done in order to prevent flaws or memory leaks from happening
ENDURANCE TESTING TOOLS
-WebLOAD
-LoadComplete
–Apache JMeter
–LoadRunner
-Appvance
-LoadUI
-OpenSTA
-Rational Performance Tester
Endurance testing is a subset of load testing in software engineering.
The procedure of endurance testing can take months or even a year.
Checks are made to confirm : Check for memory leaks, A response time test, Check your database connection, etc.