About Execution Environments and Agents
An execution environment comprises:
- An agent in Eggplant DAI
- An instance of Eggplant Functional
- A system under test (SUT).
The execution environment lets you connect a model in the Eggplant DAI web application to a suite in Eggplant Functional, and execute specific SenseTalk code snippets against a SUT.
You can access the Eggplant DAI server from any connected machine on your network with a supported browser.
What Does the Agent do?
In an execution environment, the agent makes the connection between Eggplant DAI and Eggplant Functional.
With the agent software running, and the execution environment connection active, you can attach SenseTalk snippets to actions and states in any associated Eggplant DAI model. When you run the model, it executes the SenseTalk snippets against the connected SUT. The test results can then be viewed in the console in Modeler.
You can set up and switch between execution environments in Eggplant DAI to run different sets of tests.
The agent can run on the same machine as the Eggplant DAI server, or any local or hosted machine that can connect to the Eggplant DAI server via the network. To learn how to set up an agent in an execution environment, go to Configure an Execution Environment.
For SenseTalk snippets to execute, Eggplant Functional must be installed on the same machine as the Eggplant DAI Agent software.
In Eggplant DAI 6.0 and later, the agent uses a secure access key to authenticate with Eggplant's identity and access management system.
For DAI Eggplant Cloud (Hosted DAI) users, the agent, and Fusion Engine are already included and so are the Cloud SUTs. Contact your account manager or firstname.lastname@example.org to request for DAI Eggplant Cloud.