メインコンテンツまでスキップ
バージョン: DAI 25.2

DAI Version 25.1 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.1 is the latest major release.
  • You must upgrade to Eggplant DAI 7.5.x before you start your 25.1 upgrade.
  • The upgrade may take 10-20 minutes to complete.
  • Eggplant DAI 25.1 is only compatible with Eggplant Functional 25.1.x. When you upgrade to Eggplant DAI 25.1, 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.1.1 (March 2025)​

Release 25.1.1 is a minor update to DAI that applies the following defect fixes and 3rd party updates to the 25.1.0 release.

There are no special upgrade instructions for upgrading from 25.1.0 to 25.1.1 or from 7.5.1 directly to 25.1.1.

Defect Fixes​

  • Fixes an issue where some EPF Run Log details were missing from the tabulated log layout feature that was added in 7.5.0 (CRD-1749).

  • Fixes an issue where DAI always assigns the same value to a model parameter of type "generated" (CRD-1788).

  • Fixes an issue where some users reported seeing the following error when trying to upload a suite via the Design Agent: "The selected suite is out of date with the remote version. Press download to fetch the latest version" (CRD-1779).

  • Fixes an issue where some users reported seeing the following error when more than 18 suites were added to a Git connection in DAI: "Timed out starting session on execution environment" (CRD-1789).

  • Fixes an issue with new DAI installations on machines without internet connections where some users reported seeing the following error when trying to load the license page in DAI: "Oops, you're offline" (CRD-1783).

  • Fixes a display issue where scripts in a sub folder of 635 scripts were not displaying correctly in DAI > Suites (CRD-1709).

3rd Party Updates​

Keycloak 26.1.2

Release 25.1 (February 2025)​

DAI release 25.1 includes the following enhancements and defect fixes:

ノート

You likely noticed the large jump in DAI version numbers, going from 7.5 to 25.1. To make it easier to identify compatible Eggplant products, version 25.1 and all future compatible products will share version numbers. For example, the DAI 25.1 release is compatible with Eggplant Functional 25.1, and so on.

BDD Feature File (Gherkin) Support​

DAI now supports Gherkin feature files, and their Behavior-Driven Development (BDD) test scenario format, for execution in Test Configurations. If you have feature files (with the .feature file extension) in your script suites, you can now add them as individual steps in your test configurations. You can even add feature files alongside your script-based test cases if desired. This Gherkin support also enables you to use scenario tags to filter and define the set of scenarios that will be executed within a test configuration. For more information about using Gherkin files in test configurations, see Configuring Steps/Actions for Script-based Test Cases. For more information about using Gherkin feature files, scenarios, and tags in Eggplant tests and suites, see Gherkin Integration with Eggplant Functional.

To see a video example of how you can use Gherkin feature files in DAI, click here.

ノート

When you start using Gherkin feature files in your test configurations, the scenario executions will appear as individual Test Results. You can filter the Test Results view by parent Features & Scenarios, and view the step-by-step outcomes for each scenario in the individual Test Result.

Custom Executable Scripts for Test Configurations​

To enable you to set up more flexible test conditions, DAI now allows you to add custom shell scripts that you can reuse across multiple test configurations. DAI administrators can now write their own shell scripts in batch (.bat) or shell (.sh) format (depending on the execution platform) and add them for execution in the DAI Server. Once an administrator adds a custom script, you can configure DAI to execute it before the test steps of a test configuration, allowing you immense flexibility.

A key benefit of this shell script support is the ability to synchronize from different Git branches or repositories. For example, you can use different versions of test scripts depending on your software version under test, or sync shared helper suites that reside in a separate repository from your test suites. You could also use a shell script to set up test data on your execution environment before your tests run. For more information about using custom scripts in DAI, see the new Custom Scripts page.

To see a video example of how you can use custom shell scripts with DAI, click here.

ノート

The Custom Scripts feature is disabled by default. As with any command-line level execution capability, security is an important consideration. For information about enabling the Custom Scripts feature, see the Custom Scripts page. For general information about how you can secure your DAI setup, see Securing You DAI Installation.

Better Display of Fusion Engine (EPF) Logs​

DAI 25.1 further enhances the display of test run logs from the Eggplant Functional (EPF)/Fusion Engine Sensetalk script executions. These enhancements include colorization to improve the visual experience, the ability to search and filter the logs, and the ability to click screenshot links within the logs to see a screenshot overlay in that page view. (To display run logs in DAI, navigate to the Test Results page (Controller > Test Results), and then click View > on the right side of a test listed there).

To see an example of the enhanced EPF log display, click here.

Requirements Traceability​

DAI 25.1 also enhances the user experience for the Requirements Traceability feature. You can now export a report of all the requirements statuses, and relevant mapped requirements, after a test execution. This enables you to more easily report your requirements' validation progress to management and stakeholders. For more information, see Exporting Requirements.

Other requirements traceablity improvements include the ability to view requirement descriptions alongside the requirement IDs when mapping to test cases, easier navigation to the associated test cases from the Requirements page, and the ability to delete requirement groups and associated requirements as needed.

To see a video of the requirements traceability enhancements, click here.

Defect Fixes​​

DAI 25.1 contains the following defect fixes:

  • Fixes an issue where the Millisecond Test Config time format caused the Runner page to not load (CRD-1740).

  • Fixes an issue where submodel transitions could cause an "Action has outdated parameters" error (CRD-1720).

  • Fixes an issue that occurred during DAI recovery after a penetration testing crash (CRD-1706).

  • Fixes an issue where model line numbers did not match step numbers when there is a submodel (CRD-1747).

  • Fixes an issue where DAI was generating large API logs (CRD-1737).

  • Fixes an issue with directory deletion during a DAI upgrade (CRD-1734).

Security Fixes​

DAI 25.1 remediates the following vulnerabilities:

  • Jinja has a sandbox breakout through indirect reference to format method (CVE-2024-56326 / GHSA-q2x7-8rv6-6q7h)

  • Jinja has a sandbox breakout through malicious filenames (CVE-2024-56201 / GHSA-gmj6-6f8f-6699)

  • axios 1.7.7 (BDSA-2023-4213)

  • Werkzeug 3.0.4 (CVE-2024-49767 / BDSA-2024-7832)

  • Postgres 14.13 (BDSA-2024-8514 / BDSA-2024-8512 / BDSA-2024-8452)

  • Werkzeug possible resource exhaustion when parsing file data in forms (CVE-2024-49767 / GHSA-q34m-jh98-gwm2 (ETD-5405))

  • python-jose algorithm confusion with OpenSSH ECDSA keys (GHSA-6c5p-j8vq-pqhj)

  • python-jose denial of service via compressed JWE content (GHSA-cjwg-qfpm-7377)

  • Binding to an unrestricted IP address (CWE-1327, SAST (Polaris))

3rd Party Updates​

DAI 25.1 contains the following third-party product updates:

  • RabbitMQ to 4.0.4

  • Postgres to 14.15

  • Minio to RELEASE.2024-11-07T00-52-20Z

  • Nginx to 1.26.2

  • OpenJDK to 21.0.5_11

  • Python to 3.10.16

  • MinGit to 2.47.1

Known Issues​

Gherkin execution currently does not support screenshots taken due to errors. An error screenshot will result in an exception raised in the terminal where the Run Agent is launched and in the Run Agent logs. The raised exception is a 400 Error at the /ai/screenshots endpoint with a request body dump including the screenshot's binary data. The error message will be Scenario name blank for a gherkin run despite the scenario name being populated.

に最終更新