Skip to main content
Version: DAI 25.1

Getting Started with Eggplant DAI

Upgrading from an older version?

You can find documentation for previous versions of DAI back to 6.5 by choosing the version from the drop-down menu in the upper-left corner of any page in the DAI documentation. You can find installation guides for earlier versions at the links here: 6.0, 6.1, 6.2, 6.3, 6.5.

Eggplant DAI uses a model-based approach to combine linear directed test automation with automated exploratory testing. It integrates seamlessly Eggplant Functional (EPF) and 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​

If you're new to Eggplant DAI, read the following pages and perform the following tasks to get started:

note

Some DAI components contain open source software. 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 also be provided. Please contact us with your request.

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 through running scheduled tests:

note

For information on Eggplant DAI licenses, see DAI Licensing Overview.

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.
Last updated on