Introduction
From the description of the program specification written in natural language, find the cause (input condition) and the fruit (output or program state change), can be converted to a decision table by causality diagram. Causality diagram method is a causal analysis diagram, also known as the characteristics of the chart, Ishikawa or Shark's fin chart, it is a professor of the University of Tokyo, Japan, Ishikawa put forward by a line with arrows, the quality of the relationship between the problem and the reason is a tool to analyze the factors affecting product quality. function
Causality diagram method is a kind of test method, which is suitable for describing the combination of input conditions, according to the combination of input condition, constraint relation and causality of output condition, analyzes various combinations of input conditions, and thus designs the method of test case, which is suitable for checking the various combination cases involved in the input condition of the program. The causality diagram method is used in conjunction with the decision table to determine the judging condition by mapping multiple inputs which interact simultaneously. The final result of causality diagram is the decision table, which is suitable for checking the various combinations of program input conditions. The use of Causality diagram method can help us to select a set of efficient test cases according to certain steps, and also can point out what problems exist in the specification, identify and make causality diagram. Causality diagram method focuses on the analysis of various combinations of input conditions, each combination of conditions is "because", it must have a result of the output, which is "fruit".Basic steps
The use of causality diagrams to export test cases generally takes the following steps: 1) Analyze the description of the software specification which is the reason and which is the result. The reason is the equivalence class of the input or input condition, and the result is the output condition. Give each reason and result and give an identifier, according to these relationships, draw a causal diagram. 2) The cause and effect diagram uses some marks to indicate the restriction condition or the restriction condition. 3) Analyze the requirements and represent them as diagrams between causal plots. 4) Convert the causality diagram into a decision table. 5) Use each column of the decision table as the basis for designing the test case.
Causality diagram method of software test case
