DAI 25.3 Release Notes

The notes below provide descriptions of the new features and changes introduced with each release of Eggplant DAI. You are strongly encouraged to read about the relevant changes whenever you upgrade from an earlier version.

Potential compatibility issues are highlighted.

To the extent you are entitled to a copy of the source code for the open source software distributed with this product, a free copy will be provided. Please contact us with your request.

System Requirements

You can find supported operating systems and system recommendations on the Prerequisites page.

Upgrade Notes

Before you upgrade, make sure that you stop all your DAI servers and services, and then take a backup of your database folders (data and minio) and configuration file (config.yml) before you start your installation. If there is a problem with your upgrade, you will need to restore to this point. If you have any questions or would like help testing your database before you upgrade, please contact your Technical Success Manager or our Customer Support.

• Eggplant DAI 25.3 is the latest major release.
• You must upgrade to Eggplant DAI 25.2 before you start your 25.3 upgrade.
• The upgrade may take 10-20 minutes to complete.
• Eggplant DAI 25.3 is only compatible with Eggplant Functional 25.3.x When you upgrade to Eggplant DAI 25.3, you must also update your version of Eggplant Functional.

In 25.3, the Windows on-prem version of DAI stores credentials in the Windows operating system Credential Manager (Locker). If you upgrade to 25.3, the installation will automatically move credentials that were stored in the DAI configuration file to the Windows Credential Manager. See Improves Secure Credential Management in DAI Windows On-Prem Installations in the 25.3 Release Notes below for more information.

For information about upgrading DAI container deployments, see Upgrading on the Deploying Eggplant DAI in Containers page.

The online documentation contains the latest information about DAI releases. If you are viewing this documentation online, you are seeing the latest update. If you are using the documentation embedded within DAI, please see the Release Notes on our Documentation website at: https://docs.eggplantsoftware.com/dai/dai-release-notes/ for the latest information.

Release 25.3 (August 2025)

This version of DAI includes the following enhancements and defect fixes:

Adds Support for Parallel Executions of Test Configurations

You can now run multiple instances of the same test configuration (test config) in parallel with the same, or different, filters or parameters on the DAI Runner page. (Note that this capability was available in previous versions of the Eggplant Command-Line Interface (CLI) Tool). With adequate resources available (such as sufficient SUTs, execution environments, and licenses), parallel executions enable you to run the same test config concurrently.

Examples of the benefits of parallel executions are as follows:

• You can more quickly access the results of filtered subsets of test cases in a test config. For example, you can trigger tests against feature A in the test config, then against feature B in the test config. These two sets of tests will run concurrently rather than the second set having to wait for the first set to finish.

• Similarly, you can more quickly access the results of parameterized test config runs. With parameterization, you can run the same test config against different SUT types, different locales, different data values, and so on. You can run all your variations in parallel and thereby see the outcomes sooner.

• The Runner supports the equivalent of single test case execution, just like Live Run. Now, testers and developers can run such a single test case while other scheduled/CI jobs are already running.

• Parallel executions also enable you to further reduce the quantity of your test configs because you can run tests in fewer configurations with complete flexibility, as opposed to breaking them out into many smaller ones to achieve the same end goal.

To run multiple instances of a test config at the same time, navigate to Controller > Runner and, on the test config row, click (Run), New filtered run, or Quick run (for completed runs) repeatedly the number of times for the number of instances you want to run. You can find this information in Parallel Executions of the Same Test Config on the Using the DAI Runner page in the documentation.

To see an example of how to run test configs in parallel, click here.

Moves Git Integration from Eggplant Functional (EPF) to the DAI Run Agent

As part of our ongoing work to improve flexibility in the Git repository integration, DAI 25.3 brings Git control into the DAI Run Agent as a technical improvement, rather than delegating it to EPF. This improves performance and capacity with suite syncing, and overall execution performance due to faster syncing at the start of a test config. You can also choose your preferred native Git client, giving you flexibility to control your Git setup in the way that best suits your workflow.

Enhances Logging/Reporting for Runtime Execution Overrides

DAI 25.3 provides improved run logging to ensure that any overridden parameters or test config filters are clearly output at the top of the DAI test config logs. This means you can now see at a glance the test conditions or subset filters that any given configuration execution ran with.

To see an example of the enhanced logging and reporting in action, click here.

Adds Support for Model-Based Test Config Parameterization for Global Variables

In previous releases we added parameter override capability for script-based test configs, and DAI 25.3 now enables the same capability for model-based test configs.

You can now override global parameters in model-based test configs to allow greater flexibility and reuse of your test assets. This will remove the need to duplicate test configs to change parameter values, leading to reduced test asset management overhead.

To see an example of how to override global parameters in model-based test configs click here.

Adds Eggplant Cloud Support for Hosted Execution in Containers

In DAI 25.3, Eggplant Cloud hosted execution environments (the DAI Run Agent and Eggplant Functional (EPF)) can now be provisioned in containers, so all Eggplant test activity can be, for example, entirely contained within Kubernetes clusters.

ノート

This will not immediately be done for all hosted execution customers on launch, but will progress post-launch as we transition customers gradually. Contact your Keysight Eggplant representative for more information.

Improves Secure Credential Management in DAI Windows On-Prem Installations

To improve the security of customer data for DAI Windows on-premises ("on-prem") installations, we moved any secrets held in the DAI configuration file (C:\ProgramData\Eggplant\Digital Automation Intelligence\config.yaml) to the Windows Credential Manager (Locker). Additionally, you can optionally provide secrets as environment variables, which you could use in other credential managers, for example. If an environment variable is present, then DAI uses the value of the environment variable, rather than looking in the Windows Credential Manager.

For new installations, DAI automatically uses the Windows Credential Manager. For upgrades, DAI automatically moves any secrets from the config.yaml file to the Windows Credential file.

ノート

For DAI container deployments with Kubernetes, DAI has always stored credentials in the Kubernetes secret manager.

Defect Fixes

DAI 25.3 resolves the following customer reported defects (CRDs):

• Fixes an issue where DAI test run logs were displaying a screenshot path that was not helpful. (CRD-1846)

• Fixes an issue with a message being incorrectly displayed as an error in the win_dai_service.log. (CRD-1852)

• Fixes an issue where a user was unable to add steps to a model-based test case due to performance issues. (CRD-1839)

• Fixes an issue with unsupported authentication for a Git clone. (CRD-1791)

• Fixes an issue with logging out after configuring SSO. (CRD-1857)

Security Fixes

DAI 25.3 remediates the following vulnerabilities:

• Resolves Keycloak vulnerabilities. (CVE-2024-4028, CVE-2025-2559, CVE-2025-3501, CVE-2025-3910, CVE-2025-43859)

• Resolves an issue with the DAI Agent on Windows and Linux in urllib3 version 2.3.0. (CVE-2019-20060)

• Resolves a deployment issue by providing a default value for the is_epf_started variable.

3rd Party Product Updates

DAI 25.3 contains the following third party product updates:

• Python v3.10.16 to v3.13.5 (Major upgrade)

  ノート

  The python upgrade does not apply to the Bug Hunter. If you are concerned about this, you can use Bug Hunter Lite instead.

• Version upgrade of Postgres v14 to v17.4

• Minio - RELEASE.2025-03-12T18-04-18Z to RELEASE.2025-05-24T17-08-30Z

• Nginx - 1.26.3to 1.28.0

• Open JDK - 21.0.6_7to 21.0.7_6

• RabbitMQ - 4.0.7to 4.1.1

• Keycloak - 26.2 to 26.3