Due to our audience testers have tested veterans, but also the start of a new rookie. So I prepared a foundation piece, a technical article, this is Hello, I am good, we all good! It is only when the veterans review, Reviewing the Old Well.
As a test engineer, our most basic job is to write test cases, execute test cases. And to write a special full coverage of test cases, can not be avoided, when we write test cases, add a lot of testing methods, in order to write the content of a test case. Today to talk about the commonly used test methods.
1. equivalence partitioning
Class division level is divided into equivalence classes valid, invalid ranking class. Effective equivalence classes: for the measured object, effective and reasonable, the system receives an input. Then the invalid grade class is invalid, unreasonable, not to be received from the system input. For example, a user name input defined 6-20, the input belongs to a valid equivalence class within this range. Outside the range of valid input level of classes.
2. boundary value
It refers to the boundary with respect to the input and output equivalence class equivalence class, the boundary values slightly above and some specific cases the lower limit value thereof. For example, a user name input defined 6-20, 6-19 bits may be, and other bits 5-19. City drop-down list, select the first or last, all belonging to the boundary value category.
3. The decision table
Determination table analysis and tools to perform different operations in the case of the multiple logical conditional expressions. Determination table is divided into: Condition pile, Condition, post operation, action item.
It comprises the following steps:
1. Determine the number of rules. If there are n condition. Each condition has two values (0,1), and therefore, n-th power of 2 kinds of rules.
2. List all of the conditions of piles and piles action.
3. Fill condition items.
4. Fill action item. To obtain an initial determination table.
5. simplified. Merge the similar rule
For example
Problem Description: "For the power is greater than 50 horsepower car, and maintenance records are incomplete or have been running for more than 10 years of machine maintenance treatment should be given priority."
Conditions pile:
C1: power greater than 50 horsepower it?
C2: maintenance records were incomplete it?
C3: running for more than 10 years it?
Action pile:
A1: priority processing
A2: for other processing
4. FIG causal
A plurality of controls in the interface, if there is a relationship between a combination of control or limit relationship, different combinations result in different control outputs. In order to understand the different input combinations produces output what can be causal FIG. It is expressed by the relationship between the fruit and the (output) (input the result).
For example: A = 0, and A = B, then B = 0.
5. Test outline law
Sequence comprising a plurality of windows, each window there are a plurality of functions, there are certain connections between these functions. In order to distinguish clearly between the window and the links between different window function, using the test method outline.
Such as: Test Setup
1. Analysis of functional requirements listed in the window and in each window
The outline, to find the relationship between the window and function, write test cases
6. Process Analysis
Also known as scene design method, this method for a given traffic flow.
Example: a landing system of the traffic flow, we can be divided into "basic flow", "alternative flows" "abnormal flow" scene design three use cases. The basic flow is to enter the normal user name and password, and then successfully log.
Alternate input stream is our mistake once or twice a password or user name, and enter the correct login.
Abnormal flow: enter an incorrect password or user name. Then refine the test case.
7. extrapolation error
Based on all the various possible error estimation program experience and intuition, thereby targeted test case design method that analyzes three shown below:
1. The program for all possible errors
2. The error-prone special circumstances
3. previous product testing errors have been found.
According to the above three, wrong to infer design test cases.
Of course, there are other ways, small series that is more commonly used above, there are other ways students are welcome to discuss. Xiao Bian Wang Brother VX public number of automated testing earlier published article, explain test, welcome attention.