Configuring Application Testing

Overview

Application Tests verify that your user software functions correctly and remains within established operational parameters. Similar to Load Tests, these are one-time, on-demand tests that return data and events specific to the current test. They are not scheduled to run periodically.

How It Works

An Application Test launches a single session. It only requires one session because it does not gather long-term tracking data, unlike Continuous Tests, and it does not measure aggregate performance, unlike load tests. Its sole purpose is to select a single virtual desktop infrastructure (VDI) and run a set of Application scripts to verify that your software is functional. EUX testing cannot be enabled for these tests.

Application scripts for Application Tests focus on functional areas rather than metrics. While a Continuous Test might benefit from timing every operation with measurable durations, an Application Test aims to verify that each part of the program functions correctly. The scripts should check various aspects of the program, aborting if any errors occur. If timers are used, they are intended to identify significant issues, such as tasks that never complete, rather than small speed changes.

Unlike Load Tests, Application Tests can trigger alert emails for threshold violations.

Creating an Application Test

1. In the Login Enterprise sidebar menu, navigate to Configuration > Manage Tests, and select Application Tests.

2. In Application Tests, click “+“ on the top right to create a test.

3. Define the connection settings:

4. Click Save to apply the changes.

Configuring Application Test Settings

Once you’ve created an Application Test, you need to configure the Test settings, such as:

Report Settings

You can configure the Test Report settings, such as:

You can also configure the system to send an email once the Application Test is complete. If the email notification switch is enabled but no email address is specified, the default email address from the email configuration will be used. You can enter multiple email addresses in the Email Notification field, separated by commas. For more information, see Managing Notifications.

Actions

You can add the preferred Applications for the Virtual User to test. You can also add Application Groups, and “Waits.” For details, see Configuring Applications for Testing.

Thresholds

You can also define thresholds for all Actions. These thresholds ensure that the Application not only functions correctly but also maintains its performance across different configurations. If performance thresholds are not met, you will be notified in the Application Testing report.

Access

You can assign roles to Tests to control access to the Test configuration and results. By assigning roles, only users with the designated roles will be able to view or modify the Test configuration and results, depending on their permissions. For detailed instructions on creating and managing roles, permissions, and dependencies, see the Role-Based Access Control (RBAC).

Adjusting the Engine Start Timeout

This setting works in the same way for all Test types. For details, see Adjusting the Engine start timeout.

Starting an Application Test

1. In the Application Tests, click the Play button next to the test you’d like to start.

2. After you click Play, a confirmation dialog window will appear, displaying the current Application configuration. If the configuration is correct, click Confirm to begin the test.

3. Once you click Confirm, you will be redirected to the Test Dashboard. Here, you can view the current status of your recently started Application Test. The dashboard displays how many Applications have started and if any have failed. Performance measurements are also shown. For more information, see the Test Dashboard.

Starting the Application Test from Test Config

You can run an Application Test directly from the Test configuration page. This allows you to run the Test immediately after reviewing or editing its settings, without returning to the Overview page.

Unlike Load Tests, multiple Application Tests can run at the same time. The Run Test button remains available even if other Application Tests are currently running. If there are unsaved changes, clicking Run Test will trigger a confirmation pop-up:

For Desktop Connector Tests, clicking Run Test opens the same pop-up used on the Overview page.

Best Practices: Handling Partial Failures in Scripts

Script failures are treated as an all-or-nothing outcome. If any function fails, the entire script is marked as failed. This can make it difficult to evaluate multiple functions within a single test.

If you need more granular results and want the script to continue running even after a subtask fails, consider the following approaches.

Log Subtask Failures with Events

Use CreateEvent in your script to log when a specific subtask fails.

This allows the script to:

• Record the failure in the Login Enterprise events for the Test Run.

• Continue executing the remaining subtasks.

This approach is useful when you want to capture multiple issues in a single Test Run instead of stopping at the first failure.

Use Timers to Represent Functional Results

Timers can also be used to report success or failure conditions.

Instead of measuring a duration with StartTimer and StopTimer, use SetTimer to report a predefined value.

Example approach:

• Success value: 1000 (represents 1 second)

• Failure value: 2000

Configure an alert threshold (for example, 1500) so that:

• Values below the threshold indicate success

• Values above the threshold indicate failure

Using clearly distinguishable values (such as 1000 and 2000) makes the script easier to read and maintain compared to smaller values like 1 and 2.

Application Test Results

For information on the Application Test results, see Viewing Application Testing Results.