About Test Cases

Eggplant DAI uses algorithms to generate exploratory tests that simulate user journeys. But, to run tests that take a specific, linear path through your model, you need to define test cases. For example, to make sure you have testing coverage for high priority features or for regression testing.

What is a Test Case?

A test case is a specific sequence of actions, or user journey, that you want to track when you run your model. When defining a test case, you can include a single action, or a lengthy series of actions and states that meet specific conditions. In this way, you can focus on a subset of specific paths through the model.

You can also add test cases to submodels. This means that when you run a test case which includes the linked submodel, you run the test cases for that model as well. In this way, you can monitor both model and submodel activity in the same set of results.

How do Test Cases Impact Your Testing?

Eggplant DAI uses test cases in two different ways, for:

• Exploratory testing: Each time you run a model, Eggplant DAI selects the path to follow based on its algorithms and other factors, including available test cases. These focused test cases are weighted by the path selection algorithms, which increases the probability of running the test cases that have not been hit in previous tests. When you view the results of a test run in the Console or the Logs tab, you can see which, if any, focused test cases were included in a run.

• Directed testing: After you build a test case, you can run these specific sequences manually against a model, as directed test cases. You can also add test cases for your submodels to test specific elements of your system under test.

Building and Managing Test Cases

• To start building your own test cases from scratch for models or submodels, see Building Test Cases.
• To learn more about updating, analyzing and running existing test cases, see Managing Test Cases.