Basic Theoretical Knowledge of Software Testing - Use Cases

What is a test case

Test Case (Test Case) is a set of sets provided to the system under test in order to implement the test. This set contains: test environment, operation steps, test data, expected results and other elements

Concept of Requirements

Meet user expectations or formally specify the conditions and capabilities of documents (contracts, standards, specifications), including user requirements and software requirements

Requirements-based approach to designing test cases

(1) Verify that the requirements are correct, complete, unambiguous, and logically consistent.
(2) From the perspective of "black box", design a sufficient and necessary test set to ensure that the design and code can fully meet the requirements.

Equivalent class design method (emphasis)

①Design concept: According to the requirements, the input (output will be considered in special cases) is divided into several equivalence classes, and a test case is selected from the equivalence class. If the test case passes the test, it is considered to represent theThe equivalence class test is passed, so that as many functions as possible can be covered with fewer test cases, which solves the problem that cannot be
exhaustive testing
②Effective equivalence class: It is reasonable for the specification of the program, A collection of meaningful input data, using the valid equivalence class to verify whether the program implements the functions and performance specified in the specification.

Boundary value design method (emphasis)

Design concept: Boundary value analysis is a black-box testing method to test the boundary value of input or output
Remarks: Equivalence class and boundary value are usually designed together to complement each other

Scenario Design (emphasis)

Design concept: Almost all software today uses event triggering to control the process. The scene when an event is triggered forms a scene, and the different triggering sequences and processing results of the same event form an event flow.

Bad guessing (emphasis)

Design concept: Almost all software today uses event triggering to control the process. The scene when the event is triggered forms the scene, and the different triggering sequences and processing results of the same event form the event flow

Cause and effect diagram design method (know)

①Design concept: A cause-and-effect diagram is a simplified logic diagram that can intuitively show the relationship between program input conditions (causes) and output actions (results).Cause-and-effect diagram method is a systematic method of designing test cases by means of graphs, especially suitable for various situations where the program under test has multiple input conditions and the output of the program depends on the input conditions
②Commonly usedRelationship: Identity, And, Or, Not
③Operation steps: (
(1) Analyze all possible inputs and possible outputs.
(2) Find out the correspondence between the input and the output.
(3) Draw a cause and effect diagram.
(4) Convert the cause and effect diagram into a decision table.
(5) Correspond the decision table to each test case.

Orthogonal Table Design

①Design concept: Orthogonal experimental design (Orthogonal experimental design) is a design method to study multi-factor and multi-level. It selects some representative points from all levels of experimental factors according to orthogonality.Carry out the test, understand the overall test situation by analyzing the results of this part of the test, and find the optimal level combination
②Properties:
1. Each number in each column appears the same number of times.,
2. The number of pairs of ordinal numbers formed by any two columns is the same.
③Design steps: 1. What are the factors (variables)
2. What are the levels of each factor?(values ​​of variables)
3. Select a suitable orthogonal table
4. Map the values ​​of variables to the table
5. Use the combination of the factor levels in each row as a test case
br> 6. Add the use case combination that you think is suspicious and does not appear in the table