The basic method of test case design



Equivalent zoned classification

Test case design -1

Test Case Design Method-2

Scenario:

  • Place data input, equivalence partitioning method may be used.

  • A small selection of representative data from large amounts of data for testing.

Test Ideas:

  • Divided from the large amount of data in the range, and then selected to represent the data from each range, these data can react on behalf of the test results within the range of the data.

basic concept:

  • Effective equivalence class: the program is meaningful, reasonable set of input data - used to test whether the function is implemented correctly.

  • Invalid equivalence class: the program, a meaningless, irrational set of input data - used to test whether the program has a powerful exception handling capabilities (robustness)

Design Flow:

First, make sure it's valid input range and illegal input range. For example, a name input box on its input range: 1 to 20 characters (numbers not included), then:

  • Effective equivalence class: 1 to 20 characters, do not contain numbers.

  • Invalid equivalence class: input air, is greater than 20 characters, including digital input.



Boundary value method

Often the most prone to bug at the boundary of the range of data, so in order to ensure test quality, you need to focus on testing the boundaries

Scenario:

  • There are local data input. Boundary Value and general equivalence partitioning method may be used together.

Test Ideas:

  • Representative data series selected at the boundary tested.

basic concept:

Second boundary value: point boundary value on both sides of the border called time value.

  • Minimum time boundary: the minimum effective time boundary, invalid times the minimum boundary.

  • The maximum time border: the maximum effective time boundary, invalid times the maximum boundary.

Design Flow:

  • On the second boundary values ​​one by one test.



Cause and effect diagram

Applications:

  • There are a plurality of controls in the interface, there is the relationship between a control or a combination of limits, different combinations may correspond to different inputs of the output, if you want to find out different combinations of inputs corresponding to the output of which in the end, may be causal graph / table determination method . (FIG cause / determination table method is suitable for the case of a small number of test composition, typically less than 20 kinds)

Test Ideas:

  • By way of drawing shows the relationship between the input conditions (due to) and output (fruit).

Design Flow:

  • Step 1: Find all the input conditions

  • Step 2: Find all the output results

  • Step 3: Analysis, lists all combinations of input conditions and constraints between

  • Step 4: Determine each set of input conditions will have what combination output, draw causal FIG fill determination table (FIG cause the actual work can be omitted)

  • Step 5: preparation of test cases and each column represents a combined, preparation of a test



The orthogonal collocation method

Applications:

  • In the interface has a plurality of controls, each with a plurality of values, to consider the different combinations between different values ​​of the control, and a combination of a larger number, we can use the orthogonal collocation method.

Test Ideas:

  • Minimal use of sampling data reaches the broadest, most statistics coverage.



French scene

Scenario:

  • Business more complex software systems are suitable for use scenario method, the scene is a law-based business software testing methods, the testers as the end user themselves, as real as possible operating scenarios simulated users are using this software. (Business process users correct operation - business functional verification software is implemented correctly, the situation simulated user errors - exception handling proficiency testing software (robustness))

Test Ideas:

  • Method scene when the scene is simulated users various operating software, mainly for testing software processes and business logic. When the task is to get a test, we are not the first concern of equivalence classes such as a text box meets the requirements, but the first to focus on its main functions and business processes implemented correctly, which requires law scene to complete the test. When Business Process Testing is no problem, which is the main function of the software is no problem, we worry about the equivalence classes of controls, boundary value and other details of the test. (First overall after the details)

Guess you like

Origin www.cnblogs.com/anzhengyu/p/11415020.html