End to end performance metrics can be obtained by using actual browsers, driven by virtual users.
This can be used to provide client side performance metrics while exercising a load on the backend. This is useful to understand the end to end user behavior, including the client side, when the back-end is under a certain load.
While the clients are all independent from each other, they still can be affected by the underlying load of the server(s).
So, one could put the application under a certain load, or even stress test it, and at the same time observe the behavior of individual clients.
A second use case, is to use it as a way to monitor the system and provide client side information at regular time intervals.
Based on these use cases, there are two possible ways to run Client Performance Testing:
- Combined with traditional DiveCloud load testing (to find out user experience under load)
- Use it standalone, testing one or more combinations of browsers, geographies, and bandwith (to obtain client side information of the application).
The system supports several independent browsers and browsers types.
To create a combined test plan, in addition to the data necessary to create the load testing, in the advanced options section, there is an area for browser testing, as shown in the image:
In the Browser URLs, enter one or more URLs (if multiple URLs, you need to click on the '+" icon).
The following row asks for the type of Browser, the region where to run it, and the bandwidth, which represents the type of network the device will use.
Multiple browsers can be used at the same time, by clicking on the "+" icon.
The Local DNS provides a way to replace the regular DNS, by providing a file with a list of Name-IP addresses that the system will search first before going to the official DNS.
Time to Wait between Script runs can be used to space the call to the system during the test. This can be helpful for pinging the system at regular intervals.
Threshold is similar to the load testing threshold, and is used to determine if the test passed or failed. If 0, it is ignored.
Browser Testing Only
If no load testing has to be associated to the browser testing, then it is sufficient to set the number of users (i.e. the Traffic Load field) to 0.