Home Basic SDP Test Case Web Testing FAQ Others
You are here: Home>>Test Plan & Test Case>> Test Case Design - Page 5

Sample Test Plan

you are hereQA Test Case Design


We need your help! To keep the site alive, please make the donation by clicking the button below.
Thank you very much!

How to Make a Donation Using PayPal Without an Account?
Pages: Prev 1 2 3 4 5 6 7 8 9 10 11 12 Next

Software Test Case Design

Software Testing - Software Test Case Design - Page 5

The reason, as shown in Figure 2, is that results of conditions in and and or expressions can mask or block the evaluation of other conditions. For instance, if an and condition is false, none of the subsequent conditions in the expression need be evaluated. Likewise if an or condition is true, none of the subsequent conditions need be evaluated. Hence, errors in logical expressions are not necessarily revealed by the condition-coverage and decision/condition-coverage criteria.

A criterion that covers this problem, and then some, is multiple-condition coverage. This criterion requires that you write sufficient test cases that all possible combinations of condition outcomes in each decision, and all points of entry, are invoked at least once. For instance, consider the following sequence of pseudocode.

NOTFOUND=TRUE;
DO I=1 to TABSIZE WHILE (NOTFOUND); /*SEARCH TABLE*/
...searching logic...;
END

 

The four situations to be tested are:

  1. I<=TABSIZE and NOTFOUND is true.
  2. I<=TABSIZE and NOTFOUND is false (finding the entry before hitting the end of the table).
  3. I>TABSIZE and NOTFOUND is true (hitting the end of the table without finding the entry).
  4. I>TABSIZE and NOTFOUND is false (the entry is the last one in the table).
 

Page 5


Pages: Prev 1 2 3 4 5 6 7 8 9 10 11 12 Next