The Website Performance
As far load testing, stress testing or speed or performance testing is concerned, there are a lot of overlaps between the three. Therefore, it takes an experienced and knowledgeable eye to tell the differences between the three. When all three of these tests are done, it is assumed that the software in concern has passed functionality testing. The following is a brief recap of what each one is.
Performance testing is all about run time efficiency. This is usually done under moderate load situations. What the engineer does in this situation is try and find if there are any application response problems due to resource or latency issues. It's important to remember here that these kinds of issues have more to do with the architecture, design, and implementation of the software, and not with functional bugs.
After performance testing is done, we come to load testing. This is, as the name suggests, a test done to see what kind of volume and endurance the software is capable of. The test will be done to mimic real world scenarios as close as possible. There are automated tools available to accomplish this. Volume testing is easy to understand. This is when a lot of users are mimicked using the software at the same time, within a specified amount of time. Which brings us to the next point, which would be the amount of time the software is used heavily without having a glitch.
Stress testing is about finding the software breaking point. This is done by throwing all types of scenarios at it and waiting and watching to see where and what breaks. When this is done, the engineers will be able to see how well the software degrades, and how well it recovers. Some of the ways this is accomplished is by starting and stopping it quickly, putting much more load on it than it will ever encounter, reduce hardware components such as RAM and disk space.