7.7.2   Configuring Conditions and Modifiers

The first page of the test tool wizard is explained in Table 69.

Table 69    Wizard Page 1

1	Generation path	The path leading from the root of the selection tree down to the selected modifier. Only the conditions shown here can affect the generation.
2	Selected condition test count	The number of possibilities taken into account when generating test cases where the selected condition evaluates true.
3	Total test count	The total number of test cases that are generated.
4	Test settings override	Overrides the condition-specific test settings and tells the generator only to generate one single test case.
5	Tree element specific settings	Shows the settings for the condition or modifier that is currently selected in the generation path.
6	Navigation panel	Holds buttons for closing the wizard or moving forwards and backwards in the wizard.

The test tool produces simulation cases for all the possible ways of reaching a certain modifier. The possible ways of reaching a modifier are a result of the conditions that lies on the path leading from the root of the tree down to the modifier.

The settings for a Condition determine the number of different ways that the condition can be evaluated true in a simulation. For example, a DayOfWeek condition, as seen in Figure 115, set to Monday-Wednesday is true for Monday, Tuesday, and Wednesday. In that example, three different simulation cases are generated for that condition, one for each day.

The selection tree, shown in Figure 115, is used as an example of how to use the test tool wizard.

The wizard allows the user to limit the number of simulation cases generated. This is done in the test settings pane displayed on the right hand of the wizard when selecting one of the conditions. For example, it may not be necessary to generate simulation cases for all the days in the DayOfWeek condition or all the strings in the String Field List condition. This knowledge lies with the designer of the selection tree and that is why the wizard prompts the user.

As seen in Figure 116, the DayOfWeek condition is selected. In the drop-down editor,All cases is selected, which eventually result in 3 cases (Mon, Tue, Wed). The counters shown above the settings panel in the wizard, keep track of the number of simulation cases that are generated.

The counters show both the number of cases that is required for the currently selected condition as well as the total number of simulation cases. The user should be aware that the total number of simulation cases is not a sum of the cases generated for each condition in the path. To test all the possible ways of reaching the modifiers, even cases where some of the conditions evaluate false are created.

It is possible for the user to override the condition-specific settings and let the wizard generate one single simulation case. This is done by checking the check box Only generate one single case.

When a modifier is selected, the modifier-specific settings are shown (See Figure 117). Modifier-specific test settings that are marked with a check box are validation settings. Some modifiers do not need any manual configuration. In this example, the purpose of the modifier is to set the field Number Field Validation to whatever value the Number Field field is set to.

Changes to the data outside of the generation path cannot be taken into account by the test generator and has to be recognized by the user. Therefore in this example, the Number Field Validation field should be set to the value that the user expects the field to have when the modifier is reached.