Performance Testing. Part 2: When Should I Run All These Tests?

TestFortExpert by TestFortExpert on 10/17/2014

Performance Testing. Part 2: When Should I Run All These Tests?

In the previous article we’ve spoken about different types of web performance testing. There are quite a few tests you should run to make sure your project’s performance is okay. And now as you know this you must be wondering when to run each of these.

The first thing you should remember about performance testing of your web project is that it should be done throughout the development process, not only once. Only with iterative testing can you be sure in your app performance.

Let’s look closer at how to do it, by dividing your performance testing into 5 stages which correspond to the stages in the project lifecycle:

  1. Early In the Day

When you are at the early development stage, run smoke tests to validate that your individual components work just as expected as well as that they integrate with your app and its functionality correctly. Also, component tests are run to measure the results the app’s individual components provide.

  1. At Noon

When the development is in full swing, performance testing is done to define your app’s performance characteristics such as how it performs under the normal and low load conditions, what performance issues should be improved, etc.

  1. In the Afternoon

Once you’ve tuned the individual components and checked the performance, time to test your app under its normal expected load. This will tell you how stable your app is, whether it can handle the load you expect it to, whether you need to introduce any changes, etc. After all the improvements, run the test again.

  1. Before the Show

Before launching the project, take time for doing some load tests until they are successful at some expected traffic levels. Also, soak tests are needed to determine how the app performs through some extended time period under the same load. Watch out for memory leaks and remediate them once detected. Lastly, run stress testing to know what is the load limit of your app before it fails and other issues of this kind.

  1. After the Show

Even after the launch you will still need to check for performance degradation periodically. If not the changes in the code, that amount of data your app will be using is likely to influence its performance. Thus, if you know that some upcoming event might generate increased traffic on your site, it’s necessary to make sure it’ll manage it safely. Finally, with each performance improvement, test your site again until the tests are successful.
Happy testing!

We use cookies to ensure your best experience. By continuing to browse this site, you accept the use of cookies and "third-party" cookies. For more information or to refuse consent to some cookies, please see our Privacy Policy and Cookie Policy