First, the equivalence class division method
Definition: A set of input fields, regardless of the input conditions in the set, are equivalent, if one of them cannot cause problems, in principle, there is no problem in this category
Classification: valid equivalent value (reasonable input data), invalid equivalent value (unreasonable input data)
Steps: determine input - determine input conditions - divide valid and invalid - test case coverage is valid (use the least use cases to cover as much as possible) - test case coverage is invalid (one use case covers one invalid)
Features: only test rate coverage
2. Boundary value analysis method
Upper point: point on the boundary
Distance point: the closest point to the boundary: the closed interval distance point falls outside the interval, and the open interval distance point falls within the interval
3. Orthogonal experiment method
Test combinations: automatically filter several combinations from the full permutation combination
Orthogonal Tables: Factors—Input
Install state - input value
Project - Test Case
Steps: Determine which inputs need to be combined - choose a suitable quadrature table - replace 0s and 1s with actual values
Scope of use: Combination query Compatibility test
Orthogonal table:
Multifactor Two-State Orthogonal Table
Four-Factor Three-State Orthogonal Table
Fourth, the state transition method
Concern: the correctness of state transition
Steps: Understand all possible state transitions - Draw a state transition tree - Determine test paths - Design test cases for each test path spine
Scope of use: software with working status
5. Input domain: equivalence classes and boundary values are collectively referred to as input domain
Special value test: limit value long time large input
Special Value: Millennium Bug Jan 19, 2038 3:14:07 Feb 29
6. Judgment table: whether the processing of various input rules is correct
Content: Condition pile: List all the conditions of the problem, it is usually considered that the list of conditions has nothing to do with the order
Condition item: All possible true and false values for the listed conditions
Action Stubs: List possible actions for the problem
Action item: Action should be taken under various values of the condition item
Steps: Determine all inputs and outputs (conditions and actions) - Arrange and combine all input conditions - Clarify the actions corresponding to each column and form each operation - Simplify the decision table (remove invalid rules, merge similar rules)
Scope of use: game testing
Seven, cause and effect diagram: help to quickly generate a judgment table, need to be used in conjunction with the judgment table
Relation: identity = if c is 1, then e is 1; not = if c is 1, then e is 0; or = if one of c is 1, then e is 1; and = c is 1, then e is 1
Constraints: E is different = at most one of a and b may be 1; I or = at least one of a, b, c is 1; O unique = one and only one of a, b is 1; R requires = a is 1, b must be 1;
Output condition constraints: M force = if result a is 1, then result b is forced to 0
Steps: Draw a causal diagram - split the causal diagram into small causal diagrams - form a small judgment table according to the small causal diagram - combine the small judgment tables into a large judgment table
Eight, wrong guessing method: when the number of use cases is not enough or does not meet the standard, use this method to supplement
9. Output domain test:
The output field has no invalid equivalence class
Generally only when the output is more complex may be used
Ten, process analysis method: mainly for business process testing
Steps: draw a flowchart - determine the test path (basic flow, alternative flow (success after twists and turns), abnormal flow (unsuccessful operation)) - at least one test case for each path
Scope of use: business process installation process
Concerns: Whether the process can go on, the functions in each node are not concerned
11. Anomaly analysis method
Analyze possible abnormal operations of the system or faults caused by software and hardware defects
Mainly for the fault tolerance and fault recovery ability of the system