Skip to main content
Version: DAI 25.2

DAI Version 25.2 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.2 is the latest major release.
  • You must upgrade to Eggplant DAI 25.1 before you start your 25.2 upgrade.
  • The upgrade may take 10-20 minutes to complete.
  • Eggplant DAI 25.2 is only compatible with Eggplant Functional 25.2.x. When you upgrade to Eggplant DAI 25.2, you must also update your version of Eggplant Functional.

To ensure you see the latest DAI release information, check the DAI release notes on our website at: https://docs.eggplantsoftware.com/dai/dai-release-notes/.

Release 25.2 (May 2025)​

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

Granular Control and Execution Filtering of Test Configurations​

DAI now gives you more control of your tests by allowing you to run a subset of test cases within a test configuration (test config). This enhancement means you no longer need to create multiple test configs to run different subsets of test cases in what is, in reality, one larger test suite.

This enhanced control not only gives you greater flexibility to define larger, more comprehensive test configs, but also gives you the ability to specify subsets of test cases to run from within one test config at runtime. With this granular control, you can consolidate test config assets and reduce test maintenance overhead. The ability to filter test cases from a test config at runtime is supported in the DAI GUI, command line, and CI/CD integrations. See Run selected steps on the Using the Eggplant DAI Runner page in the documentation for more information.

The filtering capability in this enhancement enables you to create multiple tags at the test case level and then set a filter on the test config run to only run the test steps with the tags you specify. For example, you can tag and define sets of tests to run as smoke tests, full regression tests, or even a specific tag to identify and exercise different system features on a specific area of your application. See Filter Options on the Using the Eggplant DAI Runner page in the documentation for more information.

Additionally, you can filter test steps by the last run. For example, you can just run the tests that failed or errored on the previous run, or by the test step name, or by scenario tags for customers using Feature file test steps. Both inclusive and exclusive filter criteria are supported.

You can also now set test cases to be ignored from a test run while still being included in the test config. The ignore option is useful, for example, in the situation where a test is ready, but the relevant feature under test is not yet included in the application. The ignore option is available on the test config Steps/actions page in the DAI app described in Step 2: Configure the Steps/Actions for the Test Configuration on the Working with Test Configurations page in the documentation.

To see an example of how the new granular control and run filtering works in DAI, click here.

Improved Test Configuration Timeout Management​

DAI now provides a system-wide maximum run duration for test configs with the option to override it at the test-config level. This maximum run duration ensures that if a test run takes longer than expected, the run will terminate at the specified time and that subsequent scheduled test runs that might require the same SUT or execution environment resources will be able to launch successfully. Any test config runs terminated by these timeouts will show a Cancelled status, and any finished test results up to that point from the test config will be available to view in DAI. See Timeout Management on the Working with Test Configurations page in the documentation for more information.

To see an example of how the new test config timeout management works in DAI, click here.

Notifications Enhancements – Webhooks​

Adding to DAI's existing capability to send email notifications about tests, you can now use webhooks to send notifications through a wider range of apps such as Microsoft Teams or Slack, or to trigger a dependent step in an external CI/CD pipeline. Webhooks give you more flexibility and control over how you stay informed and automate your workflows based on test outcomes.

To get started using webhooks, define one or more webhook profiles in which you specify the URL of the apps you want to use to send notifications. See the Webhook Notifications page in the documentation for more information.

Then, add these webhook profiles to the notification settings within your test configs. You can also define the specific test result statuses that will trigger a notification to be sent, such as when a test passes, fails, encounters an error, or is cancelled. See Notifications on the Working with Test Configurations page in the documentation for more information.

To see an example of how to configure webhook notifications in DAI for Slack, click here. Or, for a Microsoft Teams example, click here.

Optimized Launching of Eggplant Functional at Runtime​

The DAI Run Agent now only launches an instance of Eggplant Functional in an Execution Environment when it runs a test, and then terminates it when the test run finishes. Previously, EPF remained running whenever the Run Agent was running. This behavior change means EPF only uses an Execution license (or Developer license, if all Execution licenses are in use) for the duration of the test run, releasing it when the test finishes and EPF terminates. (Note that Eggplant Functional is also known as EPF or the Fusion Engine.)

DAI Release Notes are now Available by Version​

You can now navigate directly to the release notes for a specific release from the menu on the left side of the documentation pages. There is a page for each of the major DAI releases. If there are any a minor releases, those releases are included on the major release page. For example, the 7.0.1-1 release is included on the 7.0 release page.

There is also a landing page you can use that lists the release notes for the different versions. You can see it here. If you like to create bookmarks for your release notes, you might want to point it to this page.

Upgrade Version Information is now Limited to Recent Releases​

Information about how to upgrade is now only provided back to DAI version 6.5 for on the DAI Windows Upgrade and the Deploying Eggplant DAI in Containers pages.

Defect Fixes​​

DAI 25.2 contains the following defect fixes:

  • Fixes an issue on the Git connection details panel by adding a Change button under the Password/Token fields to make the change option more visible and easier to find. (CRD-1572)

  • Fixes an issue where parameter value groups were no longer generating expected values. (CRD-1769)

  • Fixes an issue where a timeout was occurring if greater than 18 suites were being synchronized by a Git connection. (CRD-1789)

Security Fixes​

DAI 25.2 remediates the following vulnerabilities:

  • Updates Axios URL handling to remediate CVE-2025-27152.

  • Upgrades Keras to v3.9 to remediate CVE-2025-1550.

  • Upgrades Serialize-Javascript to v6.0.2 to remediate CVE-2024-11831.

  • Upgrades Strawberry GraphQL to v0.257.0 to remediate CVE-2025-22151.

  • Updates Jinja string filtering to remediate CVE-2024-56326.

  • Upgrades Jinja2 to v3.1.5 to remediate CVE-2024-56201.

  • Upgrades Erlang to v26.2.5.11 to remediate CVE-2025-32433.

3rd Party Product Updates​

DAI 25.2 contains the following third party product updates:

  • Minio: RELEASE.2024-12-18T13-15-44Z to RELEASE.2025-03-12T18-04-18Z

  • Postgres: 14.15-1 to 14.17-1

  • RabbitMQ: v4.0.4 to v4.0.7

  • OpenJDK: 21.0.5_11 to 21.0.6_7

  • Nginx: 1.26.2 to 1.26.3

Last updated on