Using the New 'Host Configurator' in LoadUIWeb 2.9
Test and Monitor | Posted October 01, 2013

As part of our ongoing mission to make performance testing as easy as possible, we've added a "host configurator" to both LoadUIWeb and LoadUIWeb Pro. The host configurator enables a tester to accomplish three things very quickly and easily:

  1. Change a host globally within a scenario.
  2. Change port number for a specific host within a scenario.
  3. Turn a host or hosts on or off within a scenario.

In case the advantage of having this tool is not immediately clear, I can highlight a couple of use cases where this feature will save you time and effort in your daily routine.

USE CASE #1:  Third-Party Hosts

As we all know, websites these days make calls to numerous third-party hosts.  The home pages of retail sites can, in some cases, reference more than 100 different hosts. These hosts serve a wide variety of different purposes and some may not fit in with your performance testing goals.

With the host configurator, a list of all recorded hosts is displayed beneath your scenario.  These hosts will represent calls to:

  • Your Site
  • Image Servers
  • CDN's
  • Analytics Services
  • Ad Servers
  • Partners
  • Social Media

Although this list is far from complete, you get the idea.

In prior versions for LoadUIWeb, if you decided that you did not want to test analytics you had two options:

  1. Filter those hosts to ensure they were not recorded
  2. Delete the requests to those hosts from your scenario

In both cases, the decision was irreversible. If you later decided that you wanted to test WITH those hosts included, you would have had to re-record your scenario.

With the host configurator, you can simply uncheck the host and all calls to that host will not be simulated. If you then re-check the box, your test will once again include those hosts. It just takes a few moments to add or remove a host!

USE CASE #2:  Testing in a New Environment

Many times, testers will develop and initially run their tests in either the development or staging environment. Most of the time, these environments are different from production in a number of significant ways, including scale.

At some point, the application that you have been testing will move to production. Rather than re-record your scenario in your production environment, you can make a simple change in the configurator. After that, every place that the original host was used will now point to the new scenario.

We received requests to implement something that would cut the time necessary to re-map all of the requests to have them point to the new environment, and I think the solution is even better than what was requested!

(Note: Ports can also be changed, as sometimes a port number is the only difference.)

If you want the new configurator, just download version 2.9 - click the following link if you are a user of the free version of LoadUIWeb, and if you are an owner of LoadUIWeb Pro download it from your account.  After you've tried out the configurator, we would be interested in your feedback.

See also:

[dfads params='groups=930&limit=1&orderby=random']

[dfads params='groups=937&limit=1&orderby=random']


By submitting this form, you agree to our
Terms of Use and Privacy Policy

Thanks for Subscribing

Keep an eye on your inbox for more great content.

Continue Reading

Add a little SmartBear to your life

Stay on top of your Software game with the latest developer tips, best practices and news, delivered straight to your inbox