Alongside model execution, Eggplant DAI also lets you run test cases that are made up from Sensetalk scripts that can be scheduled much like any other test execution. This is especially useful when you want to use your scripts against more than one system under test (SUT) or when reviewing results of your project that may have both scripts and models in one location.
Creating Script Based Test Case Execution
Step-by-Step: Create Script Based Test Case Execution
In order to create a script based test case execution, follow these steps.
Go to Controller > Test Config where all your existing test configurations are listed.
From the top menu, select Add new +.
Enter the Name and Description for the test configuration to easily identify them.
(Optional) Add Tags by entering a name for the test configuration tag and pressing Enter. You can add as many tags as you need.
Specify SUT selection for the test to run on by selecting one of the following options:
- SUT by Name from the drop-down list
- SUT to use by defining one or more SUT criteria in the drop-down list. All the SUTs that are defined on the SUTs tab are available in the drop-down list. The SUT criteria field is similar to Tags, i.e., if you enter a criteria and press Enter, relevant values are populated.
The Cloud based SUTs are only available for DAI Eggplant Cloud customers only.
Select Script Based from the Type dropdown
In the Suite dropdown, select a suite from the list. This field will populate data only if you've associated at least one suite stored in Eggplant DAI. If you still can't see it, then you might want to revisit the following prerequisites:
- Connect a suite by starting a DAI Design Agent. See Connecting an Eggplant Studio Suite for more information.
- Download any suites you wish to edit in Eggplant DAI.
Select test cases to add as Steps to the test configuration. These script based test cases are associated with the suite you selected in the previous step and you can add as many test cases as you want.
Click Save. The new test configuration is saved to the list of test configurations in the Test Config tab.