LoadView emulates users on your website or server by performing specified actions on your website (device) like browsing, searching, adding products to their shopping cart etc. or generating certain types of requests to your device.

Knowing how much your device can handle helps planning further software or hardware updates and get ready for real traffic.

You can define the number of users that will be performing these actions, the duration of the LoadView test and set up a fully custom scenario with the rate of arrival/departures of those virtual users. While the test is running you can monitor the basic metrics of the test and your device in real time. Once the test is over you can review test results at any time along with the detailed responses from your device.

LoadView Device setup

To run the test, you will first need to add (the Add Device button) and set up the device and tasks. This can be done with a variety of ways. You can set up the device through the web interface, copy the device from a different platform or record the script using the Scripting Tool.

Setting up HTTP/S Tasks in the Web Interface

See the Add / Edit HTTP task article.

Load Testing Setup with an EveryStep Script

See a short series of video walkthroughs setting up a Load Test using EveryStep to record a script.

Copying a Task from a Different Platform

Choosing to copy an existing device or tasks brings up a dropdown list of platforms, and a dropdown list of devices under the selected platform.  After selecting a device, if the device has multiple tasks, you can check the tasks you wish to copy.

Configuring a LoadView Test Scenario

Once your device and tasks are set up you can configure the LoadView Test Scenario. LoadView setup involves several steps that are explained below.

Validation

Validation verifies that the tested device is valid and run without errors. Validation results status is presented in the Validation Results field, Load Device section.

Make sure the validation result is positive, otherwise click View Details and, if possible, fix the errors appeared on the Errors tab of the Performance Report

Load testing profile

Load testing profile describes simulated user behavior on a website while a task execution.

To customize simulation of user interaction with a website, see Select a Load Testing Profile.

Choosing Load Type

Load Type specifies the test execution scenario – the number of concurrent users simulated to load a device (website), the speed of load ramp-up, and the test duration.

You can configure the execution scenario manually or use the Goal-Based Load type which is automatically adjustable to your goal.

You can choose among the following load types:  

  • To verify if your website complies with the pre-determined throughput using the automatically adjustable number of simulated users, select Goal-Based Curve. This test is useful to validate SLA or non-functional requirements. 
  • To set manually a particular number of concurrent users for a specified time period and measure the response times, select Load Step Curve. It can be useful to check if your website can handle a sudden spike in traffic in order to be prepared for expected extreme traffic peaks.
  • To test the response time while adjusting the number of concurrent users manually in real time during test execution, select Dynamic Adjustable Curve.

Virtual Users Distribution (VUD)

By default, the system uses the average number of virtual users simulated per Load Injector Server, but it is recommended to use the VUD value calibrated for your device.

 If VUD exceeds the recommended value the LI Server CPU overload may occur.   

Zone Configuration

You can select cloud providers from different geo-zones that will be used to emulate virtual users. 

Summary

On the footer of the test page, you can review your LoadView test settings and get a price quote based on your settings. If you wish to adjust anything you can go back to the section you want to change and edit the settings. The LoadView price is calculated based on the following values: the cost of virtual machines required for the test, the test duration and the number of virtual users simulated during the run.

The total price includes the Load Injector Servers price and the Virtual Users price. 

At the start, you will be charged for the maximum number of simultaneous virtual users.

If the goal is reached with fewer users number than pre-defined, the difference between the Virtual Users price paid for the maximum count and the price of actual count will be refunded.

TOS

Please read the Legal agreement and accept the terms by checking the checkbox and typing your name. Note that LoadView tests that cost more than $500 will require phone verification by providing your mobile phone # and entering a confirmation code sent to the number you’ve provided. LoadView tests that cost more than $1,000 will require voice verification over the phone by our support staff that will call to a specified number.

Run

When you hit Start Test on the page you will see the status of your test and a button to cancel it. 

 If for some reason you need to stop the test, on the test summary page, click Abort. However, keep in mind that there is no money refund if virtual machines have been started already (the Starting Virtual Machines status).    

The test will go through a sequence of statuses that are explained below:

  • Submitting Test Request – sending your test settings to the server to run.
  • Starting Virtual Machines – we send cloud providers a signal to set up the required number of virtual servers and deploy virtual users. This step can take a lot of time (up to 1 hour) and you can set up to receive an email notification once it’s complete.
  • Sending Execution Scenario to Agents – we are sending LoadView scenario and tasks to the virtual users.
  • Running – this is where all the magic happens. Once the test is running you will see the charts with LoadView metrics updated in real time including the number of visitors, the number of errors if any, device response time etc.
  • Uploading Data – Once the test is over we upload all the responses from the virtual server to our server and display those responses for a more detailed analysis and review. The data retention time is 365 days for the paid version and 31 days for the trial. Please note that this step can also take a lot of time since LoadView tests generate a lot of response data.
  • Completed

Once the test is over you can review its configuration and response details at any time from the Device Manager > device action menu  > History.

To view the test results, from the History screen on the action menu of the test, open select Report. For details on available reports, see Available Stress Test reports.

 

For more information, visit www.LoadView-Testing.com