Skip to main content
Version: DAI 7.3

Getting Started with Eggplant DAI

Upgrading from an older version?

Installation guides for previous versions are available for download.

Eggplant DAI uses a model-based approach to combine linear directed test automation with automated exploratory testing. It integrates seamlessly with the Eggplant Fusion Engine for both image and object-based test execution. The use of modeling shifts the focus of testing from basic code compliance to the overall user experience by allowing data sets including real user journeys, testing coverage, and past test failures to guide new test creation. This process can be scaled across any organization, by utilizing the Eggplant DAI tools for SUT management, scheduling, and viewing results.

Why Use Eggplant DAI?

As a user, all you need to do to generate tests is build a simple model of the interface that you want to test. Eggplant DAI applies AI reasoning to auto generate the test cases based on your model. Models replicate different states, representing pages or screens that users visit, and the actions users might perform within those states or that move users between states. Eggplant DAI creates the tests from a model of the application you're testing, and integrates with Eggplant Functional (also called "Fusion Engine" when it works with DAI) to execute those tests. Creating tests using learning algorithms means that more user journeys can be tested, including those that typically, a human tester would not come up with.

Setting Up Eggplant DAI

DAI consists of the following components:

  • The DAI Server web application
  • The Execution Environment (See About Execution Environments and Agents for details)
    • The DAI Design Agent
    • The DAI Run Agent
    • Eggplant Functional (EPF)/Fusion Engine
    • Systems under test (SUTs)
  • The RLM License Server

Most DAI installations are implemented with various combinations of these components to achieve optimal test coverage and performance. The different components can run on different machines and operating systems as described on the Prerequisites page. You can run DAI on-premise or hosted in the Eggplant Cloud. DAI can also be deployed in containers as described in Deploying Eggplant DAI in Containers. Users can create and run scripts with EPF, and then use those in their models. They can use the DAI web app, and the Design Agent GUIs, and then run tests unattanded from the command line with EPF and the Run Agent. The following diagram illustrates an example DAI product implementation with multiple components so you can see how the components fit and work together.

If you're new to Eggplant DAI, you must first perform the following steps:

Then, use a workflow that suits you best. For instance, you might build models first, or define a SUT connection and test configuration, and work your way t hrough running scheduled tests:


For information on Eggplant DAI licenses, see DAI Licensing Overview. For information about how the licenses are bundled, see Eggplant DAI Licensing Bundles.

The Eggplant DAI Interface

The following section lists the components available on the left menu of the Eggplant DAI interface:

  • Dashboard: View a snapshot of the current testing status of a model and drill down into other parts of the application for more details.
  • Designer: Create and maintain the assets needed for end-to-end testing of your application. You can generate models, scripts, and test cases, as well as import user journeys based on real user data.
  • Controller: Access everything related to running tests, from defining which devices to use, to choosing what to test, to reviewing progress and outcomes of individual executions.
  • Insights: For each model, Insights present analysis relating to testing coverage and locations of defects identified in testing.
  • System: Download server log entries for all the Eggplant DAI services and view the connection status of services and connected agents.
    • Status: View the status of your system at any given time.
    • Access: Manage users, and control the level of access they have to DAI.
    • Logs: Use these logs for sending to Eggplant Support for troubleshooting. To download your server logs, click the Download button on the Logs page, which then downloads a zip file of the whole directory to the Downloads folder of your browser.
    • Licenses: Use this page to add and manage your Eggplant DAI licenses.
  • Help: Access the Eggplant DAI documentation home page for useful instructions on how to use the Eggplant DAI app.
  • Log Out: Log out of Eggplant DAI.