Traditionally in a structured test approach this involves a functional de-composition of the Functional Design Specification (FDS) down to the test condition level (the smallest atomic statement that has to be proven).
In order to apply Cause and Effect the conditions must be single logical conditions that are either true or false, yes or no, on or off etc. If one state is NOT True then the other automatically applies.
In terms of system inputs this technique is applicable for systems that use logical inputs with yes/no input combinations.
Technique steps:
In order to apply Cause and Effect the conditions must be single logical conditions that are either true or false, yes or no, on or off etc. If one state is NOT True then the other automatically applies.
In terms of system inputs this technique is applicable for systems that use logical inputs with yes/no input combinations.
Technique steps:
- Analyse the system requirements and identify the causes (input conditions) and effects (output actions)
- Produce a decision table to cover all possible combination of input conditions (rules). This will result in 2 to the power of N (where N is the number of conditions)
- Identify any infeasible rules (these are combinations that are not possible because they contain conflicting conditions e.g a book cannot be both new and second hand at the same time)
- Populate the Action (output) columns in the decision table for each rule
- Document test cases for the remaining feasible rules
No comments:
Post a Comment