automated-testing

How Blending Levels Of Automation May Assist You With Load Testing?

Low-Level Load Testing Automation

Low-level automation is what’s generally used in every load testing session. Server side performance is being verified by sets of load tests. Such tests are emulating HTTP traffic from the client side or any other low-level approach to simulating peak loads. It’s not that this will not work fine. It will but with many potential gaps that were missed during tests. Here is some approximate data that is applicable to almost any low-level load testing session:

Amounts of virtual users that may be supported by a low-level system of testing:

  • 10 to 50 HTML virtual users that are unit-based;
  • 500 to 1000 virtual users that are HTTP-oriented.

As noted above this approach may work for you and it may also leave you with several undetected issues in the future if you are not considering blending it with high-level load testing automation.

High-Level Load Testing Automation

Let us begin with why high-level approaches are used less. High-level automation interfaces require a lot of appropriate hardware. That is one of the biggest downfalls in the process. It’s not even the price that matters most. More machines are harder to manage accordingly. But the advantages of high-level automation interface usage make the decision obvious. Here are several examples of why high-level automation deserves a place on your project:

  • End-to-end server under load functionality validation. Any server that is under heavy load may cause a lot of glitches and errors in the client-side behavior.
  • Appropriate response time measurements gained from UI. It may seem possible to gather this information from single user tests and to do the math afterwards but such data will not be valid in the really heavy load scenarios. Only measurements at the UI level will grant a picture that’s more or less clear.
  • Dynamic data correlation is tested as if it’s real life. If you have done several low-level scripts that are protocol-oriented they are bond to suffer from data correlation whenever dynamic data is being returned whenever GUI automation of high-level will allow to test the way your app/browser/framework is handling such data correlations.
  • Detailed multi-user tests are possibly generated from incorporating GUI automation into load testing. This is a great boost for security of the app that may have been suffering from databases of poor design and other neglected aspects of testing.

If we are to rephrase a famous Roman leader: Combine and Conquer! Thus provide a load testing service of finest quality.


TestFort Blog

About TestFort Blog

TestFort blog is an official blog of TestFort QA Lab company and is dedicated to various QA and software testing issues.


no comments yet

Be the first to comment this post!

Would you like to share your thoughts?

Software testing & QA blog by TestFort © 2017

×