1- equivalence partitioning
Common questions divided software testing surface equivalence classes: equivalence class refers to a subset of the input field in the subset, the respective input data to expose errors in the program are equivalent and reasonable to assume..: a representative value of a test of equivalence classes of this type of test is equivalent to other values. Thus, all the input data can be divided into several reasonable equivalence class, takes a equivalence class of data as input for each of the conditions tested, a small amount can be used to achieve better test data representative of the test results can be divided into equivalence classes there are two different situations: a valid and invalid equivalence class equivalence class.
2- boundary value analysis
Boundary value analysis complements equivalence partitioning method. Testing experience tells me that a lot of errors occur at the boundaries of the input or output range, rather than occurring inside the input and output range. Therefore, design test cases for a variety of border situations, can detect more errors.
Using boundary value analysis test cases, should first determine the boundary conditions. Border equivalence class of input and output normally, that is, the case should focus on the boundary of the test should be selected exactly equal to, just greater than, or just less than the value of the boundary as the test data, whereas a typical value or an arbitrary value not selected equivalence class as the test data.
3- error reckoning
Based on all the various errors that may exist in the experience and intuition speculate program so that there are ways of targeted design test cases.
The basic idea of error guessing method: include all the possible program errors and error-prone, some special circumstances, according to their choice test cases - for example, many common errors in the module test unit had listed - previous product these are the lessons learned in testing errors have been found. Also, input data and output data is zero. Input form for the table space or enter only one line - these are prone to error. Examples of the selectable these cases as test cases.
The method of FIG causal 4-
Equivalence partitioning method and boundary value analysis method described earlier, the input conditions are important consideration, but did not consider the link between the input conditions, are combined with each other - considering combination with one another between the input conditions that may generate new case - but a combination of input conditions to be checked is not an easy task, even if all input conditions are divided into equivalence classes, the combinations between them quite a lot - must be considered suitable for a variety of conditions described in combination, to produce a corresponding plurality of actions in the form of test cases to be considered - which requires the use of cause and effect diagram (logical model) - causality FIG method final determination table is generated - it is suitable for various combinations of input conditions in the inspection procedure.
5- orthogonal table analysis
Sometimes, probably because of a combination of a number of parameters caused a surge in the number of test cases, at the same time, these test cases and no obvious gaps in priority, and testers are unable to complete such a large number of tests, it can be positive to reduce the cross-table with a number of cases, the possibility to achieve as little as possible with the embodiment to cover the largest possible range.
6- Scene Analysis Method
The user refers to the scene to simulate the user's steps, the more similar cause and effect diagram, but the depth, and may perform better feasibility.