The eighth week of the Software testing technology course

Software testing the eighth week of essays, this week the software testing course has been all over, the essay focused on the cause and Effect diagram review.

(a) Concept:

Causality diagram method is a kind of test method, which is suitable for describing the combination of input conditions, according to the combination of input condition, constraint relation and causality of output condition, analyzes various combinations of input conditions, and thus designs the method of test case, which is suitable for checking the various combination cases involved in the input condition of the program. The causality diagram method is used in conjunction with the decision table to determine the judging condition by mapping multiple inputs which interact simultaneously. The final result of causality diagram is the decision table, which is suitable for checking the various combinations of program input conditions. The use of Causality diagram method can help us to select a set of efficient test cases according to certain steps, and also can point out what problems exist in the program specification, identify and make causality diagram. Causality diagram method focuses on the analysis of various combinations of input conditions, each combination of conditions is "because", it must have a result of the output, which is "fruit".

(ii) some commonly used fixed symbols:

C: The reason (cause); Ef: Represents the result (effect); Equality:; non:;

With:; or:;

E: Exclusive (exclusive); i:at least (inclusive); r:require;

O:only one; M: Mandatory marking (marking);

(c) Example analysis:

Example: Product Description: There is a vending machine software that handles boxed drinks with a unit price of 1.5 yuan. If you invest 1.5 yuan coins, press "Cola", "Sprite", or "black tea" button, the corresponding drink will be sent out. If you invest in a 2-dollar coin, return the 5-point coin at the same time you send the drink.

The Following is a detailed procedure for designing a test case for this instance using a causal diagram:

(1) Determine the causes and results of the software requirements:

Reason: 1. Invest 1.5 yuan Coins (C1), 2. Invest 2 yuan Coins (C2), 3. Press the "Cola" button (C3);

4. Press "Sprite" button (C4), 5. Press "Black tea" button (C5);

Intermediate State; 1. Coin completion; 2. button completion;

Results: 1. Return 5 cents (EF1), 2. Send out "cola" (EF2), 3. Send "Sprite" (EF3); 4. Send out "black tea" (EF4);

(2) Determine the relationship between the cause and the result:

• Back 5 angle: ef1=c2∧ (C3∨C4∨C5) ∧e (C3,C4,C5) ∧e (C1,C2)• Cola: Ef2=c3∧ (C1∨C2) ∧e (C3,C4,C5) ∧e (C1,C2)• Sprite: Ef3=c4∧ (C1∨C2) ∧e (C3,C4,C5) ∧e (C1,C2)• Black tea: ef4=c5∧ (C1∨C2) ∧e (C3,C4,C5) ∧e (C1,C2)

(3) Draw a causal diagram:

(4) test Case Design

：

C1,C2 test cases that are set up at the same time are not achievable. However, if the programmer, the C1,C2 with two variables programming, it is possible c1,c2 at the same time set up.

Since testers cannot be tested, this is done by white-box testing.

The eighth week of the Software testing technology course