Manage Tests: Load Testing


Creating a Load Test

Configuring Load Test settings

Adding Applications to a Load Test

Starting a Load Test

Generating a Load Test report

Generating a Load Test report comparing two Tests

Load Test PDF report breakdown

Additional resources


Load Tests are designed to simulate multiple active users all running in parallel, to determine the point at which an additional user would impact existing users noticeably. Login Enterprise will launch multiple sessions on Target machines in parallel, ramping up to a specific number of sessions, with those sessions running the defined Application scripts in a repeating loop for the duration of the Test. By default, it includes the EUX data collection (see below in the “Engine Details” section) and tries to calculate a VSI Max number for your test configuration.

Load Tests are not schedulable. They must be manually started, either in the Login Enterprise > Load Testing or by making an API call. However, they require a real Connector and do not support the manual Desktop Connector. Load Tests need to be in control of session initiation to control and measure multiple sessions properly.

Load Tests will then perform the following sequence of actions:

  • Ramp up sessions based on your total number of desired logins and the number of minutes you allot to launch them. For instance, 5 users in 8 minutes would launch a new user every 2 minutes (because you always launch one at 0 minutes).
  • Once all the sessions have been launched, start counting towards the Test Duration configured in the test. (If a session fails, it is not replaced.)
  • Within each session, repeat the Application script test sequence in a continuous loop until the Test Duration has been met.
  • If configured, periodically run our EUX applications to generate an approximation of what a user will experience. Also, capture any Application script timers and other session metrics.
  • When the overall Test Duration has been met, signal all the sessions to terminate. They will terminate after the current Application script.

When you look at a Load Test, you will see a chart that shows your login sessions ramping up, and how your recorded metrics behave as your number of sessions increases. What you’re looking for are points in the curve where your metrics start to drop off as your sessions ramp up.

Note that Login Enterprise doesn’t enable alert thresholds or emails for Load tests, since these types of tests are intended to be run manually, not as a Continuous background test.

Creating a Load Test

  1. In the Sidebar menu, navigate to Configuration > Manage tests, and select Load tests.

Frame 100.png

2. In Load tests, click “+“ on the top-right.

Frame 69.png

3. In the Info window, specify the following:

a. Name - a descriptive name for this load test configuration. This name should identify the purpose or scenario of the load test.
b. Description - a brief description that outlines the objectives or specifics of this load test configuration. This helps users understand the purpose and context of the configuration.
c. Environment - the target environment where the load test will be conducted. This could include details such as server configurations, network setups, or any other relevant infrastructure information.
d. Connector - the appropriate connector that will be used to simulate the load on the target system. The connector defines how virtual users interact with the system under test.

Frame 74.png

Each Connector has its own settings. Once you define your connector, specify the necessary information in the Settings section. Here’s an example of Connector settings for the Microsoft RDS:

Frame 73.png

For more information about connectors and connection configurations, see Connectors and Connection Configurations.

4. Click Save to apply the changes.

When you delete the load test environment, only the environment itself is removed, leaving load test runs intact. However, if you delete a load test run, you will remove all associated data, including measurements, screenshots, logs, and events.

Configuring Load Test settings

For the Load test, you can configure the following settings:

a. Login - the number of users you want to be logging in in an x time (minutes).

  • The logon window is user-defined. Failed sessions won’t be retried and won’t affect the speed at which sessions log on. That is, the configured logon rate of sessions will remain the same for the logon window regardless of logon failures.
  • The logoff window is 15 minutes maximum. But the Login Enterprise will log off 10 sessions per minute minimum. So, for example, if you have a test with 140 sessions, the logoff window will take 14 minutes. Anything above 150 sessions will still take 15 minutes.

b. Test duration - how long the test will take in minutes (after the last session starts).

  • After the test duration ends all engines will stop executing the script and log off.

c. EUX Score / VSI Max - if you have EUX enabled, the Login Enterprise will calculate a VSI Max: the maximum number of sessions your resource can comfortably support. It’s assumed that a Load Test is configured to start sessions on some bounded resource group, for instance, a VDI pool that points exclusively to one dedicated test server. You could then calculate the VSI Max for that single server, and use that to determine how many servers you need for a fixed number of user desktops.

Arguably, VSI Max is the whole point of Load Tests, so if you’re not using the Login VSI EUX code, you’d still be looking to see what the maximum number of concurrent sessions your system can support is before your metrics start to drop off. So even if we’re not able to calculate VSImax for you, the Login Enterprise graphs may show you the point where your analysis shows performance degradation.

The Login Enterprise calculated VSI Max is defined to be the point where the EUX Score drops below 5.5, and that point is marked on the EUX metrics graph. (This calculation may change in future releases, but it’s always intended to convey the point where responsiveness gets subjectively bad).

Now that you’ve configured Load Test settings, you can add applications to your Load Test.

Adding Applications to a Load Test

For the Load Test, you can add the preferred applications for the Virtual User to test. You can also add Application groups and an option “to wait”. To do this:

In Actions, click the green “+“ to add a new action, and select what you’re going to add in the pop-up window.

Frame 76.png

You can reorder applications along with the "Wait" action under the List of actions. To do this, click on the application drag-and-drop area and organize them in the order you want your Login Enterprise to run the applications.

You can also adjust the configuration to "leave applications running" or "run once" for an application. Leave Application running does not close the application. Run Once will only run the script once.

Frame 77.png

Now that you have all your test configurations in place, you can start a Load Test.

Starting a Load Test

1. In the Sidebar menu, navigate to Configuration > Manage tests, and select Load tests.

2. In the Load test, click "play" next to the test you’d like to start.

Frame 78.png

When you start the Load test, Login Enterprise will attempt to reserve the necessary accounts and selected launchers. These resources will be exclusively allocated for use by load testing during its execution. If Continuous Test tries to use these accounts or launchers at the same time, it won't be allowed. This could mean there aren't enough resources for Continuous testing.

3. To start the test, click Confirm.

Frame 79.png

Once the Load test starts, you are redirected to the Test dashboard where you can see the Load test and its progression. To view the early results of your Load test, in the Test dashboard click on the Load test that you started.

Frame 80.png

For more information on how to interpret the Load Test results, see Load Testing Results.

Generating a Load Test Report

Starting from Login Enterprise 5.8, you can download a PDF report with the results of your Load Test. 

The Load Test Report covers such subject areas as Test Details, Test Results, Login and Application specifics, EUX Score, and metrics to characterize system performance. It serves as a valuable resource in understanding the performance of your system under different workloads and implementing necessary improvements.

To generate a Load Test Report:

1. In the Sidebar menu, navigate to Results > Load testing.

Frame 70.png

2. In the Load testing results, click “>“ (right arrow) next to the test you’re interested in.

Frame 71.png 

3. Click Generate PDF report (A browser pop-up will open).

Frame 72.png

4. In the browser pop-up, click Save to save the PDF report.

Alternatively, select the checkbox next to the specific test, and in the top menu toolbar, click Generate PDF report.

Frame 85.png

Generating a PDF report comparing two Load Tests

Starting from Login Enterprise 5.9, you can generate and download a PDF report comparing the results of two Load Tests. You can do this in one of the following ways:

a. Using the toolbar on the Load test results page:

Frame 85.png

b. Using the Generate PDF report button on the Compare page:

Frame 107.png

Load test PDF report breakdown

The PDF report summarizes the findings obtained from the Load Testing process. It includes the following:

1. General information including Introduction, EUX Score, and Metrics.

Frame 108.png

2. Test specifics, such as the product version, EUX version, VSI Max version, Connector, Launcher group, number of users, Test duration, Date, and Workload.

Frame 109.png

3. Test results: all the results, such as Success rates (table), EUX score (table), and VSI Max (table).

Frame 110.png

4. Charts, including the EUX Score, EUX timers, and Logins specific charts with Display protocol connection, Profile load, GPO processing, and Total login time.

Frame 111.png

Frame 112.png

5. Application-specific charts

    • Depending on the scripts/workloads attached to the Test, the report will contain a chart for each timer.

Frame 117.png

6. Session Metrics charts

    • Depending on the Session Metrics linked to the Test, each session metric will have its own chart

Frame 118.png

Frame 119.png

Important information

Active sessions and login window finished:

  • In a single Load Test PDF report, all charts will include lines for active sessions and the login window finished line.
  • In a PDF report comparing two Load Tests, all charts will include lines for active sessions, but none will include the login window finished line.

Comparing logic:

  • The report will determine which test is compared to which, mirroring the UI. To switch the Tests in the report, switch them in the UI first, then generate the PDF report.
  • The Test considered as the baseline will be labeled "Baseline" in tables.

EUX & VSI Max-related messages

The EUX and VSI Max information, warning, and error messages are shown in the comment column within their respective tables.

Additional resources

  • For the accounts and account groups, see Accounts.
  • For information about the launchers, see Launchers.

If you have questions or need additional information on specific Load Test configurations, feel free to get in touch with our support at