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.
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. Users can link from here to other parts of the application for more detail.
Designer: Create and maintain the assets needed for end-to-end testing of your application. You can generate models, scripts, and test cases manually or automatically here, 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, the Insights section presents analysis relating to testing coverage, locations of defects identified in testing, and progress through groups of test cases.
System: Download server log entries for all the Eggplant DAI services. These logs can be sent to Eggplant Support for troubleshooting. To download your server logs, click the Download button in the Logs tab, which then downloads a zip file of the whole directory in the Downloads folder of your browser.
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.
Using Eggplant DAI
To start using Eggplant DAI, you must first:
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:
- Working with Models in Modeler
- Managing SUTs
- Executing tests Via Test Configuration
- Viewing Test Results
- Using the Designer