1. Set test points for exhaustive scenarios:
1) Method: equivalence class.
2) Equivalence classes are divided into: valid equivalence and invalid equivalence.
①Effective equivalence: within the range of test data, take one.
② Invalid equivalence: All values outside the range are invalid, and one of each is selected.
3) The focus is on the type of verification.
Validation lengths use boundary values, validation rules and types use equivalence classes.
2. Set test points for the bounding boundary rules:
1) Method: Boundary value.
2) Main verification points:
① Upper point: point on the boundary.
②From point: the point closest to the previous point.
③Inner point: the point within the range.
3) There are at most 7 use cases in the design test point using the boundary pair length limit, and there are 5 use cases after optimization.
4) Optimization method: open inside and close outside.
① If the upper point is not included in the open interval, the inner point is taken.
②The closed interval includes the upper point, and the outer point is taken.
5) For a single input box, the method of boundary value + equivalence class is generally used for design.
3. Set test points for multi-condition dependencies:
1) Method: Judgment table.
2) Design test points:
①Condition pile: extract the condition.
② Action Pile: A list of final results that can be produced.
③Condition item: yes, no, no yes, no no.
④Action item: the value is right or wrong.
3) Multiple conditions may not necessarily have dependencies, such as: phone number, address.
4) The decision table is only used for multiple conditional dependencies.
5) The number of conditions determines the number of use cases: 2 to the power of conditions = the number of use cases.
4. Set test points for the project business:
1) Method: flowchart method (scene method).
2) Key points: test the business first, and then test the single function and single module.