Load view 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 to real traffic.
You can define the number of users that will be performing these actions, the duration of the Load view 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.
To run the test, you will first need to 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. Once your device and tasks are set up you can configure the Load view test.
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.
Load Testing Setup with an EveryStep Script
Here is a short series of video walkthroughs setting up a Load Test using EveryStep to record a script. EveryStep can be used to setup an HTTP/S only task by selecting HTTP/S (HTML download only), or a fully rendered script in a real browser by selecting the browser of choice.
Load view set up involves several steps that are explained below.
Once you have added a task to a test, simply press the Calibrate button and wait for the Calibration results to appear. Calibration is an important part of the set up because it verifies that the Task(s) are valid and run without errors as well as determines the maximum recommended number of virtual users per virtual machine based upon the task complexity and resources required to execute it.
The result of calibration will set the default value for the Number of Virtual Users per Virtual Machine setting in the Virtual Users Distribution section. Along with the Execution plan this setting will influence the number of Virtual servers the test will require.
This section is where you set up the test duration, number of simultaneous visitors and their arrival/departure rate. Load curve chart on the right will give you a visual representation of traffic to the device and how it will change over the course of the test.
This section allows you to select Cloud providers that will be used to emulate virtual users. Number of virtual servers and the number of virtual users on each server will be calculated automatically based on the Load view scenario, number of zones and the calibration results. However, you can adjust distribution of servers and thus users between different zones. Different zones may have different pricing. Also, each Load view test will have 1 Reference server that will run just 1 virtual user. You cannot remove that server or change the number of virtual users on it. This user represents an outside visitor that will test device availability during the test. Also in case of the user view tasks we will shoot video of task executions for that reference user. You can later use it for further review and analysis.
Virtual Users Distribution
This section allows you to adjust the number of virtual users per virtual server. This is a very important setting that influences the price and the quality of the Load view test.
The price of the test depends on the number of virtual servers. The number of virtual servers in turn depends on the task and the number of user per virtual servers that is determined during the calibration process.
You can increase the Number of Virtual Users per Virtual Server setting based on your preferences and reduce the number of servers. However, caution should be taken since increasing this value may lead to Virtual server hitting its CPU limit, failing to load the device with the specified number of users and distort test results.
On this 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 previous page and edit the settings. The Load view price is calculated based on the following values: The Cost of Virtual Machines required for the test, the duration of the test and number of virtual users simulated during the run.
Please read the Legal agreement and accept the terms by checking the checkbox and typing your name. Note that Load view 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. Load view 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.
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. 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 Load view scenario and tasks to the virtual users.
- Running – This is where all the magic happens J. Once the test is running you will see the charts with Load view metrics updated in real time including Number of visitors, 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. Please note that this step can also take a lot of time since Load view tests generate a lot of response data.
Once the test is over you can review its configuration and response details at any time from the history page of the device.