Test case preconditions

Preconditions for a test case offer hints to the tester as to what should be checked or adjusted at SUT before actual execution of a test case. Such preconditions can be identical for all test cases but can also differ from each other de­pen­ding on the test case.

Since most test case management systems often provide a field for preconditions, LF‑ET generates a precondition from all preconditions that should be drawn for a specific test case. Within a decision table preconditions can be created in different places with different effects:

  1. Test case preconditions for a decision table. Such preconditions are recorded for each test case.

  2. Test case preconditions for a specific rule. Such preconditions are only taken over in a specific test case if the test case has been ge­ne­ra­ted for the corresponding rule or the rule is contained in the rule sequence for which this specific test case has been ge­ne­ra­ted.

  3. Test case preconditions for a condition. Such a precondition is only taken over in the specific test case when the corresponding condition is specified for the rule, which means that either a specific value of the value table is contained in the value table or the "irrelevant" entry should be specified for a specific value.

  4. Test case conditions for the value of a condition. This precondition is only taken over in the test case if the corresponding value of a condition is used in the rule for which the specific test case is ge­ne­ra­ted.

  5. Test case preconditions for an action. This precondition is taken over in the test case to be ge­ne­ra­ted if one of the possible values of the action is defined in the rule for the corresponding action.

  6. Test case preconditions for the value of an action. Such a precondition is taken over in the test case to be ge­ne­ra­ted if the corresponding value in which the precondition is provided is defined in the rule.