What are the common software test case design methods

1. According to whether to view the internal structure of the program, it is divided into:

1) Black box testing.

2) White box testing.

2. According to whether the program is running, it is divided into:

1) Static test (static

testing）：

2) Dynamic testing.

3. Divided by stages:

1) Unit tests.

2) Integration testing.

3) System testing.

4) Acceptance test.

4. Black box testing is divided into functional testing and performance testing

5. Other test types:

Regression testing. Smoke test.

Random testing. Test case design methodology.

1) Step-by-step subdivision method (2) Input domain test method.

3) Output domain analysis.

4) Orthogonal experimental design method.

5) Business process analysis.

6) State transition method.

7) Cause and Effect Diagram Method.

8) Judgment table method.

9) Misguessing method.

10) Equivalence class division method.

11) Boundary value analysis.

Equivalence class division method for software test case design.

1. Definition of the equivalence class division method.

2. Terminology of the equivalence class division method.

3. The principle of equivalence class division.

4. Example demonstration (triangle problem and file management system problem) of boundary value analysis method for software test cases.

1. Definition of boundary value analysis method.

2. The difference between the equivalence class division method and the boundary value analysis method.

3. Internal boundary values.

Fourth, the principle of designing test cases.

5. Example of boundary value analysis (triangle problem).

Error guessing method for software test case design.

1. Definition of erroneous speculation.

2. The basic idea of the erroneous speculation method.

3. Examples of erroneous speculation.

4. Advantages and disadvantages of the erroneous speculation method.

Decision table-driven approach to software test case design.

1. Definition of the Judgment Table.

2. Components of the Judgment Table.

3. Design steps of the decision table-driven method.

4. Examples. 5. The difference between a cause and effect diagram and a decision table.

6. Determine the conditions for the use of the table-driven method.

7. Advantages of the judgment table-driven method.

8. Disadvantages of the table-driven method.

Causal diagram method for software test case design.

1. Definition of causal diagram method.

2. Common symbols for cause and effect diagrams.

3. The four relationships of cause and effect diagrams.

4. Constraints on cause and effect diagrams.

5. Design steps of the causal diagram method.

6. Examples.

1. One of the ways to design test cases using black box technology is the causal diagram method.

2. White box testing is a test case design method, the box refers to the software being tested, and the white box refers to the fact that the box is visible, so that you can understand what is inside the box and how it works inside. The white-box approach provides a comprehensive understanding of the program's internal logical structure and tests all logical paths. The white-box method is an exhaustive path test.

3. The unit test mainly adopts the white-box test technology, and the test cases are designed by controlling the virtual slag flow coverage and data flow coverage. The main test content includes unit function test, unit performance test, and exception handling test.

4. It is divided into two parts: outline design and detailed design, and the software is realized: the software is converted into a program acceptable to the computer** software testing: on the basis of the design of test cases, the various components of the software are inspected, and the software is put into operation in the software operation and maintenance stage, and is continuously maintained in use, and the necessary expansion and deletion are carried out.

5. The process of software testingThe process of software testing generally includes several stages, such as test plan, test design, test execution, test report and defect management.

Based on the input conditions, input values, or number of inputs, it is divided into valid equivalence classes and invalid equivalence classes.

Select representative inputs from the valid equivalence class and the invalid equivalence class to form test cases, and avoid redundant use cases with the same test effect.

It is usually used in conjunction with the boundary value method.

1. Determine the valid equivalence class and the invalid equivalence class according to each input condition.

2. The equivalence classes of different input conditions do not need to be combined, that is, they do not need to be traversed through all combinations. It only takes that every equivalent class is overridden.

1. The input condition clarifies the range of values.

2. The number of values is specified in the input condition.

3. The input condition is clearly an ordered set.

1. In addition to considering the boundary value, it is also necessary to consider the value near the boundary value.

2. Take a valid value in the same range.

Perform different operations on the combined values of different logical conditions.

Conditional stakes (all conditions of the problem) Conditional items (true or false values under all possible conditions) Action stakes (actions that the problem prescribes to be taken) Action items (actions that should be taken in the case of various values of conditional terms).

Testing of multiple states as well as switching conditions and switching paths between states.

1. Draw a state migration diagram, including the migration direction and migration conditions.

2. Design the use case to cover all paths.