1. Why use the test method of cause and effect diagram test cases?
In the process of designing test cases, the decision table design method considers the constraint relationship between input and input, but does not consider the constraint relationship between input and output. Simple business logic can be solved with decision tables, but complex constraints are not suitable.
2. What is cause and effect diagram design?
In the design process of software test cases, the cause and effect diagram is used to describe the constraint relationship between input and input, input and output.
For the requirements specification, the causes and effects are divided into 2 groups of 4 categories: input and output, input and input.
The relationship between input and output mainly includes: identity, not, and, or
Identity: If the input condition occurs, the corresponding output must be generated; if the input condition does not occur, the corresponding output must not be generated
Not: If the input condition occurs, the corresponding output will not be generated. If the input condition does not occur, the corresponding output will definitely be generated.
AND: Multiple input conditions, only when all input conditions occur, the corresponding output will be generated
Or: In multiple input conditions, as long as one occurs, the corresponding output will be generated.
There are also 4 relationships between input and input, such as exclusive, or, unique, and requirement.
Exclusive (at least one of all input conditions occurs, and none of the conditions can occur)
or (all input conditions at least one input condition occurs, and multiple conditions can coexist)
Unique (all input conditions have one and only one occurrence)
Requirement (as long as one of all input conditions occurs, the other inputs will also occur)
3. What are the steps to design a test case in a cause-and-effect diagram?
1. Determine the cause (input) and result (output) according to the needs
2. Draw a cause-and-effect diagram according to the relationship between input and output in the demand, and the relationship between input and input
3. Draw the judgment table, and get the final judgment table according to the cause and effect diagram
4. Obtain the use case rules according to the judgment table, and refine the test cases by combining the equivalence class and the boundary value use case design method
4. What are the pros and cons of designing test cases with cause and effect diagrams?
Advantages: It can help test case designers quickly understand requirements, understand business logic, and then quickly design decision tables to obtain the required test cases. This method can be used in systems with complex causal relationships.
Disadvantage: Pay attention to the size of the rules when using them
5. An example of a cause-and-effect diagram design test case?
Step 1: Find out the input (cause) and output (result) according to your needs
Input (reason): first column is A (C1) first column is B (C2) second column is number (C3)
Intermediate node: the first column is A or B (C12)
Output (fruit): output M (E1), modify file (E2), output L (E3)
Step 2: Put the causes of the same type together, connect the intermediate nodes of similar causes, and place the corresponding results on the opposite side. Easy to connect
Step 3: Draw a judgment table according to the relationship between the input and output of the causal diagram, and remove the non-conforming rules in the table according to the relationship between the input and input of the causal diagram
Fourth: Extract test rules according to the decision table, write test cases, and refine and supplement test cases with equivalence class division and boundary value