I. Steps for designing a test case using the causal method:
1. analyze the software specification to describe the cause (that is, the equivalence class of the input condition or input condition) and the result (that is, the output condition), and assign an identifier to each reason and result.
2. Analyze the semantics in the description of the Software specification, find out the relationship between the cause and the result, and between the cause and the reason, and draw the cause based on these relationships.
3. constraints: Due to syntax or environmental restrictions, the combination between the cause and the result is impossible for some reasons and causes. To indicate these special circumstances, use some marks to indicate constraints or restrictions on the cause and effect.
4. Convert the causal indicator into a discriminant table.
5. Take each column of the Decision Table out as a test case based on the design.
II. Steps for designing test cases using the scenario method:
1. Describe the basic flow of the program and various alternative flows according to the specifications.
2. generate different scenarios based on the Basic stream and various alternative streams
3. generate corresponding test cases for each scenario. You can use matrices or decision tables to determine and manage test cases.
4. Review the generated test cases, remove unnecessary or equivalent test cases, and then determine the actual test data.
3. Steps for designing test cases using the basic path method:
1. Draw the control flow diagram of the program
2. Circle complexity of computing programs
3. Export Test Cases
Note: The minimum number of use cases covered by the Branch: generally equal to the number of decision statements in the program plus 1, that is, the number of minutes. For example, there are three if statements with four branches in total.
Steps for designing test cases