Chapter 8 Software Testing-1

Software Engineering (3 rd ed.), By K.
K Aggarwal & Yogesh Singh, Copyright © New Age International Publishers, 2007 1
Software Testing
• What is Testing?
Many people understand many definitions of testing :
1. Testing is the process of demonstrating that errors are not present.
2. The purpose of testing is to show that a program performs its intended

functions correctly.
3. Testing is the process of establishing confidence that a program does

what it is supposed to do.
These definitions are incorrect.
Software Engineering (3 rd ed.), By K.K Aggarwal & Yogesh Singh, Copyright © New Age International Publishers, 2007 2
Software Testing
A more appropriate definition is:
“Testing is the process of executing a program with

the intent of finding errors.”
Software Testing
• Why should We Test ?
Although software testing is itself an expensive activity, yet launching of

software without testing may lead to cost potentially much higher than that
of testing, specially in systems where human safety is involved.
In the software life cycle the earlier the errors are discovered and removed,
the lower is the cost of their removal.
Software Testing
• Who should Do the Testing ?

o Testing requires the developers to find errors from their software.
o It is difficult for software developer to point out errors from own
creations.
o Many organisations have made a distinction between development
and testing phase by making different people responsible for each
phase.
Software Testing
• What should We Test ?
We should test the program’s responses to every possible input. It means,

we should test for all valid and invalid inputs. Suppose a program requires
two 8 bit integers as inputs. Total possible combinations are 2 8x28. If only
one second it required to execute one set of inputs, it may take 18 hours to
test all combinations. Practically, inputs are more than two and size is also
more than 8 bits. We have also not considered invalid inputs where so
many combinations are possible. Hence, complete testing is just not
possible, although, we may wish to do so.
Software Testing
Fig. 1: Control flow graph

Software Testing
The number of paths in the example of Fig. 1 are 10 14 or 100 trillions. It is
computed from 520 + 519 + 518 + …… + 51; where 5 is the number of paths
through the loop body. If only 5 minutes are required to test one test path, it
may take approximately one billion years to execute every path.
Software Testing
Some Terminologies
 Error, Mistake, Bug, Fault and Failure
People make errors. A good synonym is mistake. This may be a syntax
error or misunderstanding of specifications. Sometimes, there are logical
errors.
When developers make mistakes while coding, we call these mistakes

“bugs”.
A fault is the representation of an error, where representation is the mode

of expression, such as narrative text, data flow diagrams, ER diagrams,
source code etc. Defect is a good synonym for fault.
A failure occurs when a fault executes. A particular fault may cause

different failures, depending on how it has been exercised.
Software Testing
 Test, Test Case and Test Suite
Test and Test case terms are used interchangeably. In practice, both are
same and are treated as synonyms. Test case describes an input
description and an expected output description.
Test Case ID
Section-I Section-II
(Before Execution) (After Execution)
Purpose : Execution History:
Pre condition: (If any) Result:
Inputs: If fails, any possible reason (Optional);
Expected Outputs: Any other observation:

Post conditions: Any suggestion:
Written by: Run by:
Date: Date:
Fig. 2: Test case template
The set of test cases is called a test suite. Hence any combination of test
cases may generate a test suite.
Software Testing
 Verification and Validation
Verification is the process of evaluating a system or component to

determine whether the products of a given development phase satisfy the
conditions imposed at the start of that phase.
Validation is the process of evaluating a system or component during or at
the end of development process to determine whether it satisfies the
specified requirements .
Testing= Verification+Validation
Software Testing
 Alpha, Beta and Acceptance Testing
The term Acceptance Testing is used when the software is developed for
a specific customer. A series of tests are conducted to enable the customer
to validate all requirements. These tests are conducted by the end user /
customer and may range from adhoc tests to well planned systematic
series of tests.
The terms alpha and beta testing are used when the software is developed
as a product for anonymous customers.
Alpha Tests are conducted at the developer’s site by some potential
customers. These tests are conducted in a controlled environment. Alpha
testing may be started when formal testing process is near completion.
Beta Tests are conducted by the customers / end users at their sites.
Unlike alpha testing, developer is not present here. Beta testing is
conducted in a real environment that cannot be controlled by the
developer.
Software Testing
Functional Testing
Input Output
domain domain
System
Input test Output
under
data test data
test
Fig. 3: Black box testing
Software Testing
Boundary Value Analysis
Consider a program with two input variables x and y. These input variables
have specified boundaries as:
a≤x≤b
c≤y≤d
Input domain
d
y
c
a b
x
Fig.4: Input domain for program having two input variables
Software Testing
The boundary value analysis test cases for our program with two inputs
variables (x and y) that may have any value from 100 to 300 are:
(200,100), (200,101), (200,200), (200,299), (200,300), (100,200), (101,200),
(299,200) and (300,200). This input domain is shown in Fig. 8.5. Each dot represent
a test case and inner rectangle is the domain of legitimate inputs. Thus, for a
program of n variables, boundary value analysis yield 4n + 1 test cases.
Input domain
400
300
y 200
100
0 100 200 300 400

x
Fig. 5: Input domain of two variables x and y with
boundaries [100,300] each
Software Testing
Example- 8.I
Consider a program for the determination of the nature of roots of a

quadratic equation. Its input is a triple of positive integers (say a,b,c) and
values may be from interval [0,100]. The program output may have one of
the following words.
[Not a quadratic equation; Real roots; Imaginary roots; Equal roots]
Design the boundary value test cases.
Software Testing
Solution
Quadratic equation will be of type:

ax2+bx+c=0
Roots are real if (b2-4ac)>0
Roots are imaginary if (b2-4ac)<0
Roots are equal if (b2-4ac)=0
Equation is not quadratic if a=0
Software Testing
The boundary value test cases are :
Test Case a b c Expected output
1 0 50 50 Not Quadratic
2 1 50 50 Real Roots
3 50 50 50 Imaginary Roots
9 50 100 50 Equal Roots
Software Testing
Example – 8.2
Consider a program for determining the Previous date. Its input is a triple of
day, month and year with the values in the range
1 ≤ month ≤ 12
1 ≤ day ≤ 31
1900 ≤ year ≤ 2025
The possible outputs would be Previous date or invalid input date.
Software Testing
Solution
The Previous date program takes a date as input and checks it for validity.
If valid, it returns the previous date as its output.
With single fault assumption theory, 4n+1 test cases can be designed and
which are equal to 13.
Software Testing
The boundary value test cases are:
Test Case Month Day Year Expected output
1 6 15 1900 14 June, 1900

2 6 15 1901 14 June, 1901
3 6 15 1962 14 June, 1962
4 6 15 2024 14 June, 2024
5 6 15 2025 14 June, 2025
6 6 1 1962 31 May, 1962
7 6 2 1962 1 June, 1962
8 6 30 1962 29 June, 1962
9 6 31 1962 Invalid date

10 1 15 1962 14 January, 1962
11 2 15 1962 14 February, 1962

12 11 15 1962 14 November, 1962
13 12 15 1962 14 December, 1962
Software Testing
Example – 8.3
Consider a simple program to classify a triangle. Its inputs is a triple of

positive integers (say x, y, z) and the date type for input parameters ensures
that these will be integers greater than 0 and less than or equal to 100. The
program output may be one of the following words:
[Scalene; Isosceles; Equilateral; Not a triangle]
Software Testing
Solution
The boundary value test cases are shown below:
Test case x y z Expected Output
1 50 50 1 Isosceles
2 50 50 2 Isosceles
3 50 50 50 Equilateral
4 50 50 99 Isosceles
5 50 50 100 Not a triangle
6 50 1 50 Isosceles
7 50 2 50 Isosceles
Software Testing
Robustness testing
It is nothing but the extension of boundary value analysis. Here, we would
like to see, what happens when the extreme values are exceeded with a
value slightly greater than the maximum, and a value slightly less than
minimum. It means, we want to go outside the legitimate boundary of input
domain. This extended form of boundary value analysis is called
robustness testing and shown in Fig. 6
There are four additional test cases which are outside the legitimate input
domain. Hence total test cases in robustness testing are 6n+1, where n is
the number of input variables. So, 13 test cases are:
(200,99), (200,100), (200,101), (200,200), (200,299), (200,300)

(200,301), (99,200), (100,200), (101,200), (299,200), (300,200), (301,200)
Software Testing
400
300
y 200
100
0 100 200 300 400

x
Fig. 8.6: Robustness test cases for two variables x

and y with range [100,300] each
Software Testing
Worst-case testing
If we reject “single fault” assumption theory of reliability and may like to see
what happens when more than one variable has an extreme value. In
electronic circuits analysis, this is called “worst case analysis”. It is more
thorough in the sense that boundary value test cases are a proper subset
of worst case test cases. It requires more effort. Worst case testing for a
function of n variables generate 5n test cases as opposed to 4n+1 test
cases for boundary value analysis. Our two variables example will have
52=25 test cases and are given in table 1.
Software Testing
Table 1: Worst cases test inputs for two variables example
Test case Inputs Test case Inputs

number number
x y x y
1 100 100 14 200 299

2 100 101 15 200 300
3 100 200 16 299 100
4 100 299 17 299 101
5 100 300 18 299 200
6 101 100 19 299 299
7 101 101 20 299 300
8 101 200 21 300 100
9 101 299 22 300 101
10 101 300 23 300 200
11 200 100 24 300 299
12 200 101 25 300 300
13 200 200 --
Software Testing
Example - 8.4
Consider the program for the determination of nature of roots of a quadratic

equation as explained in example 8.1. Design the Robust test case and
worst test cases for this program.
Software Testing
Solution
Robust test cases are 6n+1. Hence, in 3 variable input cases total number
of test cases are 19 as given on next slide:
Software Testing
Test case a b c Expected Output
1 -1 50 50 Invalid input`
2 0 50 50 Not quadratic equation
3 1 50 50 Real roots
4 50 50 50 Imaginary roots
7 101 50 50 Invalid input

8 50 -1 50 Invalid input
12 50 100 50 Equal roots
14 50 50 -1 Invalid input
Software Testing
In case of worst test case total test cases are 5n. Hence, 125 test cases will be
generated in worst test cases. The worst test cases are given below:
Software Testing
Test Case A b c Expected output

27 1 0 1 Imaginary
28 1 0 50 Imaginary
29 1 0 99 Imaginary
30 1 0 100 Imaginary
31 1 1 0 Real Roots
Software Testing
Test Case A b C Expected output
32 1 1 1 Imaginary
33 1 1 50 Imaginary
34 1 1 99 Imaginary
44` 1 99 99 Real Roots
Software Testing

50 1 100 100 Real Roots
52 50 0 1 Imaginary
57 50 1 1 Imaginary
Software Testing
75 50 100 100 Imaginary
77 99 0 1 Imaginary
82 99 1 1 Imaginary
Software Testing
100 99 100 100 Imaginary
Software Testing

105 100 0 100 Imaginary
110 100 1 100 Imaginary
111 100 50 0 Real Roots
112 100 50 1 Real Roots
113 100 50 50 Imaginary
114 100 50 99 Imaginary
115 100 50 100 Imaginary
116 100 99 0 Real Roots
117 100 99 1 Real Roots
118 100 99 50 Imaginary
Software Testing
119 100 99 99 Imaginary

120 100 99 100 Imaginary
121 100 100 0 Real Roots
122 100 100 1 Real Roots
123 100 100 50 Imaginary
124 100 100 99 Imaginary
125 100 100 100 Imaginary
Software Testing
Example – 8.5
Consider the program for the determination of previous date in a calendar as

explained in example 8.2. Design the robust and worst test cases for this
program.
Software Testing
Solution
Robust test cases are 6n+1. Hence total 19 robust test cases are designed
and are given on next slide.
Software Testing
Test case Month Day Year Expected Output
1 6 15 1899 Invalid date (outside range)
2 6 15 1900 14 June, 1900
3 6 15 1901 14 June, 1901

4 6 15 1962 14 June, 1962
5 6 15 2024 14 June, 2024
6 6 15 2025 14 June, 2025
7 6 15 2026 Invalid date (outside range)

9 6 1 1962 31 May, 1962
10 6 2 1962 1 June, 1962
11 6 30 1962 29 June, 1962
15 1 15 1962 14 January, 1962
16 2 15 1962 14 February, 1962

17 11 15 1962 14 November, 1962
18 12 15 1962 14 December, 1962
Software Testing
In case of worst test case total test cases are 5n. Hence, 125 test cases will be
generated in worst test cases. The worst test cases are given below:
1 1 1 1900 31 December, 1899

2 1 1 1901 31 December, 1900
3 1 1 1962 31 December, 1961
4 1 1 2024 31 December, 2023
5 1 1 2025 31 December, 2024
6 1 2 1900 1 January, 1900
7 1 2 1901 1 January, 1901
8 1 2 1962 1 January, 1962
9 1 2 2024 1 January, 2024
10 1 2 2025 1 January, 2025
11 1 15 1900 14 January, 1900
12 1 15 1901 14 January, 1901
13 1 15 1962 14 January, 1962
14 1 15 2024 14 January, 2024
Software Testing
15 1 15 2025 14 January, 2025

16 1 30 1900 29 January, 1900
17 1 30 1901 29 January, 1901
18 1 30 1962 29 January, 1962
19 1 30 2024 29 January, 2024
20 1 30 2025 29 January, 2025
21 1 31 1900 30 January, 1900
22 1 31 1901 30 January, 1901
23 1 31 1962 30 January, 1962
24 1 31 2024 30 January, 2024
25 1 31 2025 30 January, 2025
26 2 1 1900 31 January, 1900
27 2 1 1901 31 January, 1901
28 2 1 1962 31 January, 1962
29 2 1 2024 31 January, 2024
30 2 1 2025 31 January, 2025
31 2 2 1900 1 February, 1900
Software Testing
32 2 2 1901 1 February, 1901

33 2 2 1962 1 February, 1962
34 2 2 2024 1 February, 2024
35 2 2 2025 1 February, 2025
36 2 15 1900 14 February, 1900
37 2 15 1901 14 February, 1901
38 2 15 1962 14 February, 1962
39 2 15 2024 14 February, 2024
40 2 15 2025 14 February, 2025
Software Testing

51 6 1 1900 31 May, 1900
52 6 1 1901 31 May, 1901
53 6 1 1962 31 May, 1962
54 6 1 2024 31 May, 2024
55 6 1 2025 31 May, 2025
56 6 2 1900 1 June, 1900
57 6 2 1901 1 June, 1901
58 6 2 1962 1 June, 1962
59 6 2 2024 1 June, 2024
60 6 2 2025 1 June, 2025
61 6 15 1900 14 June, 1900
62 6 15 1901 14 June, 1901
63 6 15 1962 14 June, 1962
64 6 15 2024 14 June, 2024
65 6 15 2025 14 June, 2025
Software Testing
66 6 30 1900 29 June, 1900

67 6 30 1901 29 June, 1901
68 6 30 1962 29 June, 1962
69 6 30 2024 29 June, 2024
70 6 30 2025 29 June, 2025
76 11 1 1900 31 October, 1900
77 11 1 1901 31 October, 1901
78 11 1 1962 31 October, 1962

79 11 1 2024 31 October, 2024
80 11 1 2025 31 October, 2025
81 11 2 1900 1 November, 1900
82 11 2 1901 1 November, 1901
Software Testing
83 11 2 1962 1 November, 1962

84 11 2 2024 1 November, 2024
85 11 2 2025 1 November, 2025
86 11 15 1900 14 November, 1900
87 11 15 1901 14 November, 1901
88 11 15 1962 14 November, 1962
89 11 15 2024 14 November, 2024
90 11 15 2025 14 November, 2025
91 11 30 1900 29 November, 1900
92 11 30 1901 29 November, 1901
93 11 30 1962 29 November, 1962
94 11 30 2024 29 November, 2024
95 11 30 2025 29 November, 2025
Software Testing
101 12 1 1900 30 November, 1900

102 12 1 1901 30 November, 1901
103 12 1 1962 30 November, 1962
104 12 1 2024 30 November, 2024
105 12 1 2025 30 November, 2025
106 12 2 1900 1 December, 1900
107 12 2 1901 1 December, 1901
108 12 2 1962 1 December, 1962
109 12 2 2024 1 December, 2024
110 12 2 2025 1 December, 2025
111 12 15 1900 14 December, 1900
112 12 15 1901 14 December, 1901
113 12 15 1962 14 December, 1962
114 12 15 2024 14 December, 2024
115 12 15 2025 14 December, 2025
116 12 30 1900 29 December, 1900
117 12 30 1901 29 December, 1901
118 12 30 1962 29 December, 1962
Software Testing
119 12 30 2024 29 December, 2024

120 12 30 2025 29 December, 2025
121 12 31 1900 30 December, 1900
122 12 31 1901 30 December, 1901
123 12 31 1962 30 December, 1962
124 12 31 2024 30 December, 2024
125 12 31 2025 30 December, 2025
Software Testing
Example – 8.6
Consider the triangle problem as given in example 8.3. Generate robust and
worst test cases for this problem.
Software Testing
Solution
Robust test cases are given on next slide.
Software Testing
` x y z Expected Output
1 50 50 0 Invalid input`
2 50 50 1 Isosceles
3 50 50 2 Isosceles

9 50 1 50 Isosceles
Software Testing
Worst test cases are 125 and are given below:
Test Case x y z Expected output
1 1 1 1 Equilateral
7 1 2 2 Isosceles
Software Testing

27 2 1 2 Isosceles
31 2 2 1 Isosceles
Software Testing
45 2 99 100 Scalene
Software Testing
49 2 100 50 Scalene
53 50 1 2 Isosceles
58 50 2 2 Isosceles
Software Testing
Test Case A B C Expected output
70 50 99 100 Scalene
74 50 100 99 Scalene
75 50 100 100 Isosceles
Software Testing
85 99 2 100 Scalene
90 99 50 100 Scalene
97 99 100 2 Scalene
98 99 100 50 Scalene
100 99 100 100 Isosceles
Software Testing

105 100 1 100 Isosceles
109 100 2 99 Scalene
110 100 2 100 Isosceles
114 100 50 99 Scalene
115 100 50 100 Isosceles
117 100 99 2 Scalene
118 100 99 50 Scalene
Software Testing
119 100 99 99 Isosceles

120 100 99 100 Isosceles
121 100 100 1 Isosceles
122 100 100 2 Isosceles
123 100 100 50 Isosceles
124 100 100 99 Isosceles
Software Testing
Equivalence Class Testing
In this method, input domain of a program is partitioned into a finite number of
equivalence classes such that one can reasonably assume, but not be
absolutely sure, that the test of a representative value of each class is
equivalent to a test of any other value.
Two steps are required to implementing this method:
1. The equivalence classes are identified by taking each input condition and
partitioning it into valid and invalid classes. For example, if an input condition
specifies a range of values from 1 to 999, we identify one valid equivalence
class [1<item<999]; and two invalid equivalence classes [item<1] and
[item>999].
2. Generate the test cases using the equivalence classes identified in the
previous step. This is performed by writing test cases covering all the valid
equivalence classes. Then a test case is written for each invalid equivalence
class so that no test contains more than one invalid class. This is to ensure
that no two invalid classes mask each other.
Software Testing
Invalid input
Valid System
Outputs
inputs under test
Input domain Output domain
Fig. 7: Equivalence partitioning
Most of the time, equivalence class testing defines classes of the input domain.
However, equivalence classes should also be defined for output domain.
Hence, we should design equivalence classes based on input and output
domain.
Software Testing
Example 8.7
Consider the program for the determination of nature of roots of a quadratic
equation as explained in example 8.1. Identify the equivalence class test
cases for output and input domains.
Software Testing
Solution
Output domain equivalence class test cases can be identified as follows:
O1={<a,b,c>:Not a quadratic equation if a = 0}

O2={<a,b,c>:Real roots if (b2-4ac)>0}
O3={<a,b,c>:Imaginary roots if (b2-4ac)<0}
O4={<a,b,c>:Equal roots if (b2-4ac)=0}`
The number of test cases can be derived form above relations and shown
below:
Test case a b c Expected output
1 0 50 50 Not a quadratic equation
4 50 100 50 Equal roots
Software Testing
We may have another set of test cases based on input domain.
I1= {a: a = 0}
I2= {a: a < 0}
I3= {a: 1 ≤ a ≤ 100}
I4= {a: a > 100}
I5= {b: 0 ≤ b ≤ 100}
I6= {b: b < 0}
I7= {b: b > 100}
I8= {c: 0 ≤ c ≤ 100}
I9= {c: c < 0}
I10={c: c > 100}
Software Testing
1 0 50 50 Not a quadratic equation

2 -1 50 50 Invalid input
4 101 50 50 invalid input
6 50 -1 50 invalid input
9 50 50 -1 invalid input
Here test cases 5 and 8 are redundant test cases. If we choose any value other
than nominal, we may not have redundant test cases. Hence total test cases are
10+4=14 for this problem.
Software Testing
Example 8.8
Consider the program for determining the previous date in a calendar as
explained in example 8.3. Identify the equivalence class test cases for output
& input domains.
Software Testing
Solution
Output domain equivalence class are:
O1={<D,M,Y>: Previous date if all are valid inputs}

O1={<D,M,Y>: Invalid date if any input makes the date invalid}
Test case M D Y Expected output

1 6 15 1962 14 June, 1962
Software Testing
We may have another set of test cases which are based on input domain.
I1={month: 1 ≤ m ≤ 12}
I2={month: m < 1}
I3={month: m > 12}
I4={day: 1 ≤ D ≤ 31}
I5={day: D < 1}
I6={day: D > 31}
I7={year: 1900 ≤ Y ≤ 2025}
I8={year: Y < 1900}
I9={year: Y > 2025}
Software Testing
Inputs domain test cases are :
Test Case M D Y Expected output
1 6 15 1962 14 June, 1962

2 -1 15 1962 Invalid input
4 6 15 1962 14 June, 1962
5 6 -1 1962 invalid input
7 6 15 1962 14 June, 1962
8 6 15 1899 invalid input (Value out of range)
9 6 15 2026 invalid input (Value out of range)
Software Testing
Example – 8.9
Consider the triangle problem specified in a example 8.3. Identify the

equivalence class test cases for output and input domain.
Software Testing
Solution
Output domain equivalence classes are:
O1={<x,y,z>: Equilateral triangle with sides x,y,z}

O1={<x,y,z>: Isosceles triangle with sides x,y,z}
O1={<x,y,z>: Scalene triangle with sides x,y,z}
O1={<x,y,z>: Not a triangle with sides x,y,z}
The test cases are:
3 100 99 50 Scalene
Software Testing
Input domain based classes are:
I1={x: x < 1}
I2={x: x > 100}
I3={x: 1 ≤ x ≤ 100}
I4={y: y < 1}
I5={y: y > 100}
I6={y: 1 ≤ y ≤ 100}
I7={z: z < 1}
I8={z: z > 100}
I9={z: 1 ≤ z ≤ 100}
Software Testing
Some inputs domain test cases can be obtained using the relationship amongst x,y
and z.
I10={< x,y,z >: x = y = z}

I11={< x,y,z >: x = y, x ≠ z}
I12={< x,y,z >: x = z, x ≠ y}
I13={< x,y,z >: y = z, x ≠ y}
I14={< x,y,z >: x ≠ y, x ≠ z, y ≠ z}
I15={< x,y,z >: x = y + z}
I16={< x,y,z >: x > y +z}
I17={< x,y,z >: y = x +z}
I18={< x,y,z >: y > x + z}
I19={< x,y,z >: z = x + y}
I20={< x,y,z >: z > x +y}
Software Testing
Test cases derived from input domain are:
Software Testing
14 100 99 50 Scalene
Software Testing
Decision Table Based Testing
Condition Entry
Stub
True False
C1
True False True False

C2
C3 True False True False True False ---
Action a1 X X X
Stub
a2 X X X
Table 2: Decision table terminology
a3
X X
Software Testing
Test case design
C1:x,y,z are sides of a triangle? N Y

C2:x = y? -- Y N
C3:x = z? -- Y N Y N
C4:y = z? -- Y N Y N Y N Y N
a1: Not a triangle X
a2: Scalene X
a3: Isosceles X X X
a4: Equilateral X
a5: Impossible X X X
Table 3: Decision table for triangle problem

Software Testing
Conditions F T T T T T T T T T T
C1 : x < y + z ?
C2 : y < x + z ? -- F T T T T T T T T T
C3 : z < x + y ? -- -- F T T T T T T T T
C4 : x = y ? -- -- -- T T T T F F F F
C5 : x = z ? -- -- -- T T F F T T F F
C6 : y = z ? -- -- -- T F T F T F T F
a1 : Not a triangle X X X
a2 : Scalene X
a3 : Isosceles X X X
a4 : Equilateral X
a5 : Impossible X X X
Table 4: Modified decision table

Software Testing
Example 8.10
Consider the triangle program specified in example 8.3. Identify the

test cases using the decision table of Table 4.
Software Testing
Solution
There are eleven functional test cases, three to fail triangle property, three
impossible cases, one each to get equilateral, scalene triangle cases, and
three to get on isosceles triangle. The test cases are given in Table 5.
4 5 5 5 Equilateral
5 ? ? ? Impossible
6 ? ? ? Impossible
7 2 2 3 Isosceles
8 ? ? ? Impossible
9 2 3 2 Isosceles
10 3 2 2 Isosceles
11 3 4 5 Scalene
Test cases of triangle problem using decision table

Software Testing
Example 8.11
Consider a program for the determination of Previous date. Its input is a triple of day,
month and year with the values in the range
1 ≤ month ≤ 12
1 ≤ day ≤ 31
1900 ≤ year ≤ 2025
The possible outputs are “Previous date” and “Invalid date”. Design the test
cases using decision table based testing.
Software Testing
Solution
The input domain can be divided into following classes:
I1= {M1: month has 30 days}
I2= {M2: month has 31 days except March, August and January}
I3= {M3: month is March}
I4= {M4: month is August}
I5= {M5: month is January}
I6= {M6: month is February}
I7= {D1: day = 1}
I8= {D2: 2 ≤ day ≤ 28}
I9= {D3: day = 29}
I10={D4: day = 30}
I11={D5: day = 31}
I12={Y1: year is a leap year}
I13={Y2: year is a common year}
Software Testing
The decision table is given below:
Sr.No. 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
C1: Months in M1 M1 M1 M1 M1 M1 M1 M1 M1 M1 M2 M2 M2 M2 M2
C2: days in D1 D1 D2 D2 D3 D3 D4 D4 D5 D5 D1 D1 D2 D2 D3
C3: year in Y1 Y2 Y1 Y2 Y1 Y2 Y1 Y2 Y1 Y2 Y1 Y2 Y1 Y2 Y1
a1: Impossible X X
a2: Decrement day X X X X X X X X X
a3: Reset day to 31 X X
a5: Reset day to 29
a6: Reset day to 28
a7: decrement month X X X X
a8: Reset month to December
a9: Decrement year
Software Testing
Sr.No. 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30
a1: Impossible
a2: Decrement day X X X X X X X X X X X X X
a3: Reset day to 31
a4: Reset day to 30
a5: Reset day to 29 X
a6: Reset day to 28 X
a7: decrement month X X
a9: Decrement year

Software Testing
Sr.No. 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45
a1: Impossible
a2: Decrement day X X X X X X X X X X X
a3: Reset day to 31 X X X X
a4: Reset day to 30
a5: Reset day to 29
a6: Reset day to 28
a8: Reset month to December X X
a9: Decrement year X X
Software Testing
Sr.No. 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60
a1: Impossible X X X X X
a2: Decrement day X X X X X X X X
a4: Reset day to 30
a5: Reset day to 29
a6: Reset day to 28
a9: Decrement year

Software Testing
Test case Month Day Year Expected output
1 June 1 1964 31 May, 1964
2 June 1 1962 31 May, 1962
3 June 15 1964 14 June, 1964
4 June 15 1962 14 June, 1962
5 June 29 1964 28 June, 1964
6 June 29 1962 28 June, 1962
7 June 30 1964 29 June, 1964
8 June 30 1962 29 June, 1962
9 June 31 1964 Impossible
10 June 31 1962 Impossible
11 May 1 1964 30 April, 1964
12 May 1 1962 30 April, 1962
13 May 15 1964 14 May, 1964
14 May 15 1962 14 May, 1962
15 May 29 1964 28 May, 1964
Software Testing
16 May 29 1962 28 May, 1962
17 May 30 1964 29 May, 1964
18 May 30 1962 29 May, 1962
19 May 31 1964 30 May, 1964
20 May 31 1962 30 May, 1962
21 March 1 1964 29 February, 1964
22 March 1 1962 28 February, 1962
23 March 15 1964 14 March, 1964
24 March 15 1962 14 March, 1962
25 March 29 1964 28 March, 1964
26 March 29 1962 28 March, 1962
27 March 30 1964 29 March, 1964
28 March 30 1962 29 March, 1962
29 March 31 1964 30 March, 1964
30 March 31 1962 30 March, 1962
Software Testing
31 August 1 1964 31 July, 1962
32 August 1 1962 31 July, 1964
33 August 15 1964 14 August, 1964
34 August 15 1962 14 August, 1962
35 August 29 1964 28 August, 1964
36 August 29 1962 28 August, 1962
37 August 30 1964 29 August, 1964
38 August 30 1962 29 August, 1962
39 August 31 1964 30 August, 1964
40 August 31 1962 30 August, 1962
41 January 1 1964 31 December, 1964
42 January 1 1962 31 December, 1962
43 January 15 1964 14 January, 1964
Software Testing
51 February 1 1964 31 January, 1964
52 February 1 1962 31 January, 1962
53 February 15 1964 14 February, 1964
56 February 29 1962 Impossible
Software Testing
Cause Effect Graphing Technique
 boundary value analysis and equivalence class Consider single input
conditions
 It is used because boundary value analysis and equivalence class
partitioning methods do not explore combinations of input
circumstances
Steps
1. Causes & effects in the specifications are identified.
A cause is a distinct input condition or an equivalence class of input conditions.
An effect is an output condition or a system transformation.
2. The semantic content of the specification is analysed and transformed into a
boolean graph linking the causes & effects.
3. Constraints are imposed
4. graph – limited entry decision table

Each column in the table represent a test case.
5. The columns in the decision table are converted into test cases.
Software Testing
The basic notation for the graph is shown in fig. 8
Fig.8. 8 : Basic cause effect graph symbols
Software Testing
Myers explained this effectively with following example. “The characters in column 1
must be an A or B. The character in column 2 must be a digit. In this situation, the
file update is made. If the character in column 1 is incorrect, message x is issued. If
the character in column 2 is not a digit, message y is issued”.
The causes are
c1: character in column 1 is A
c2: character in column 1 is B
c3: character in column 2 is a digit
and the effects are

e1: update made
e2: message x is issued
e3: message y is issued
Software Testing
Fig. 9: Sample cause effect graph
Software Testing
The E constraint states that it must always be true that at most

one of c1 or c2 can be 1 (c1 or c2 cannot be 1 simultaneously). The
I constraint states that at least one of c 1, c2 and c3 must always be
1 (c1, c2 and c3 cannot be 0 simultaneously). The O constraint
states that one, and only one, of c 1 and c2 must be 1. The
constraint R states that, for c1 to be 1, c2 must be 1 (i.e. it is
impossible for c1 to be 1 and c2 to be 0),
Software Testing
Fig. 10: Constraint symbols

Software Testing
Fig. 11: Symbol for masks constraint
Software Testing
Fig. 12 : Sample cause effect graph with exclusive constraint
Software Testing
Example 8.12
Consider the triangle problem specified in the example 8.3. Draw the Cause
effect graph and identify the test cases.
Software Testing
Solution
The causes are
c 1: side x is less than sum of sides y and z
c 2: side y is less than sum of sides x and y
c 3: side z is less than sum of sides x and y
c 4: side x is equal to side y
c 5: side x is equal to side z
c 6: side y is equal to side z
and effects are

e1: Not a triangle
e2: Scalene triangle
e3: Isosceles triangle
e4: Equilateral triangle
e5: Impossible stage
Software Testing
The cause effect graph is shown in fig. 13 and decision table is shown in table 6.
The test cases for this problem are available in Table 5.
Conditions
C1: x < y + z ? 0 1 1 1 1 1 1 1 1 1 1
C2: y < x + z ? X 0 1 1 1 1 1 1 1 1 1
C3: z < x + y ? X X 0 1 1 1 1 1 1 1 1
C4: x = y ? X X X 1 1 1 1 0 0 0 0
C5: x = z ? X X X 1 1 0 0 1 1 0 0
C6: y = z ? X X X 1 0 1 0 1 0 1 0
e1: Not a triangle 1 1 1
e2: Scalene 1
e3: Isosceles 1 1 1
e4: Equilateral 1
e5: Impossible 1 1 1
Table 6: Decision table

Software Testing
Fig. 13: Cause effect graph of triangle problem

Software Testing
Structural Testing
A complementary approach to functional testing is called structural / white box
testing. It permits us to examine the internal structure of the program.
Path Testing
Path testing is the name given to a group of test techniques based on judiciously
selecting a set of test paths through the program. If the set of paths is properly
chosen, then it means that we have achieved some measure of test thoroughness.
This type of testing involves:
1. generating a set of paths that will cover every branch in the program.
2. finding a set of test cases that will execute every path in the set of program
paths.
Software Testing
Flow Graph
The control flow of a program can be analysed using a graphical representation
known as flow graph. The flow graph is a directed graph in which nodes are either
entire statements or fragments of a statement, and edges represents flow of control.
Fig. 14: The basic construct of the flow graph
Software Testing
Software Testing
Software Testing
Software Testing
Software Testing
Fig. 15: Program for previous date problem

Software Testing
Fig. 16: Flow graph of previous date

problem
Software Testing
DD Path Graph
Table 7: Mapping of flow graph nodes and DD path nodes
Flow graph DD Path graph Remarks
nodes corresponding
node
1 to 9 n1 There is a sequential flow from node 1 to 9
10 n2 Decision node, if true go to 13 else go to 44
13,14 n5 Sequential nodes and are combined to form new node n5
15,16,17 n6 Sequential nodes
18 n7 Edges from node 14 to 17 are terminated here
20 n9 Intermediate node with one input edge and one output edge
22 n11 Intermediate node
Cont….
Software Testing

nodes corresponding
node
24,25 n13 Sequential nodes
26 n14 Two edges from node 25 & 23 are terminated here
27 n15 Two edges from node 26 & 21 are terminated here. Also a decision node
36 n20 Three edge from node 29,32 and 35 are terminated here
43 n24 Three edge from node 36,39 and 42 are terminated here
Cont….
Software Testing
nodes corresponding
node
44 n25 Decision node, if true go to 45 else go to 82. Three edges from 18,43 & 10
are also terminated here.
47,48,49,50 n28 Sequential nodes
52 n30 Intermediate node with one input edge & one output ege
58 n35 Two edge from node 57 and 55 are terminated here
59 n36 Decision node, if true go to 60 else go to 63. Two edge from nodes 58 and
53 are terminated.
Cont….
Software Testing
nodes corresponding
node
67 n39 Two edge from node 62 and 66 are terminated here
76 n43 Four edges from nodes 50, 67, 71 and 75 are terminated here.
80 n45 Two edges from nodes 76 & 79 are terminated here
85 n48 Two edges from nodes 81 and 84 are terminated here
86,87 n49 Sequential nodes with exit node
Software Testing
Fig. 17: DD path graph

of previous date
problem
Software Testing
Fig. 18: Independent paths of previous date problem

Software Testing
Example 8.13
Consider the problem for the determination of the nature of roots of a quadratic
equation. Its input a triple of positive integers (say a,b,c) and value may be from
interval [0,100].
The program is given in fig. 19. The output may have one of the following words:
[Not a quadratic equation; real roots; Imaginary roots; Equal roots]
Draw the flow graph and DD path graph. Also find independent paths from the DD
Path graph.
Software Testing
Cont….
Software Testing
Fig. 19: Code of quadratic equation problem

Software Testing
Solution
Fig. 19 (a) : Program flow

graph
Software Testing
Fig. 19 (b) : DD Path graph

Software Testing
The mapping table for DD path graph is:
nodes corresponding
node
1 to 10 A Sequential nodes
11 B Decision node
12 C Intermediate node
13 D Decision node
14,15 E Sequential node
16 F Two edges are combined here
17 G Two edges are combined and decision node
18 H Intermediate node
19 I Decision node
20,21 J Sequential node
22 K Decision node
23,24,25 L Sequential node
Software Engineering (3 rd ed.), By K.K Aggarwal & Yogesh Singh, Copyright © New Age International Publishers, 2007
Cont…. 123
Software Testing
nodes corresponding
node
26,27,28,29 M Sequential nodes
30 N Three edges are combined
31 O Decision node
32,33 P Sequential node
34,35,36 Q Sequential node
37 R Three edges are combined here
38,39 S Sequential nodes with exit node
An Independent path is any path through the DD path graph that introduces at least
one new set of processing statements or new conditions. Therefore, an independent
path must move along at least one edge that has not been traversed before the path
is defined.
Independent paths are:
(i) ABGOQRS (ii) ABGOPRS
(iii) ABCDFGOQRS (iv) ABCDEFGOPRS
(v) ABGHIJNRS (vi) ABGHIKLNRS
(vi) ABGHIKMNRS
Software Testing
Example 8.14
Consider a program given in Fig.8.20 for the classification of a triangle. Its input is a
triple of positive integers (say a,b,c) from the interval [1,100]. The output may be
[Scalene, Isosceles, Equilateral, Not a triangle].
Draw the flow graph & DD Path graph. Also find the independent paths from the DD
Path graph.
Software Testing
Software Testing
Fig. 20 : Code of triangle classification problem
Software Testing
Solution :
Flow graph of
triangle problem is:
Fig.8. 20 (a): Program flow graph
Software Testing
The mapping table for DD path graph is:
nodes corresponding
node
1 TO 9 A Sequential nodes
10 B Decision node
11 C Decision node
12, 13 D Sequential nodes
14 E Two edges are joined here
15, 16, 17 F Sequential nodes

18 G Decision nodes plus joining of two edges
19 H Decision node
20, 21 I Sequential nodes
22 J Decision node
23, 24 K Sequential nodes
25, 26, 27 L Sequential nodes
Cont….
Software Testing

nodes corresponding
node
28 M Three edges are combined here
29 N Decision node
30, 31 O Sequential nodes
32, 33, 34 P Sequential nodes
35 Q Three edges are combined here
36, 37 R Sequential nodes with exit node
Fig. 20 (b): DD Path graph
Software Testing
DD Path graph is given in Fig. 20 (b)
Independent paths are:

(i) ABFGNPQR
(ii) ABFGNOQR
(iii) ABCEGNPQR
(iv) ABCDEGNOQR
(v) ABFGHIMQR
(vi) ABFGHJKMQR
(vii)ABFGHJMQR
Fig. 20 (b): DD Path graph
Software Testing
Cyclomatic Complexity
McCabe’s cyclomatic metric V(G) = e – n + 2P.

For example, a flow graph shown in in Fig. 21 with entry node ‘a’ and exit node ‘f’.
Fig. 21: Flow graph

Software Testing
The value of cyclomatic complexity can be calculated as :
V(G) = 9 – 6 + 2 = 5
Here e = 9, n = 6 and P =1
There will be five independent paths for the flow graph illustrated in Fig. 21.
Path 1 : a c f
Path 2 : a b e f
Path 3 : a d c f
Path 4 : a b e a c f or a b e a b e f
Path 5 : a b e b e f
Software Testing
Several properties of cyclomatic complexity are stated below:
1. V(G) ≥1
2. V (G) is the maximum number of independent paths in graph G.
3. Inserting & deleting functional statements to G does not affect V(G).
4. G has only one path if and only if V(G)=1.
5. Inserting a new row in G increases V(G) by unity.
6. V(G) depends only on the decision structure of G.
Software Testing
The role of P in the complexity calculation V(G)=e-n+2P is required to be understood
correctly. We define a flow graph with unique entry and exit nodes, all nodes
reachable from the entry, and exit reachable from all nodes. This definition would
result in all flow graphs having only one connected component. One could, however,
imagine a main program M and two called subroutines A and B having a flow graph
shown in Fig. 22.
Fig. 22
Software Testing
Let us denote the total graph above with 3 connected components as
V ( M  A  B)  e  n  2 P
= 13-13+2*3
=6
This method with P  1 can be used to calculate the complexity of a

collection of programs, particularly a hierarchical nest of subroutines.
Software Testing
Notice that V ( M  A  B )  V ( M )  V ( A)  V ( B )  6 . In general, the

complexity of a collection C of flow graphs with K connected components is
equal to the summation of their complexities. To see this let C i,1 ≤ I ≤ K
denote the k distinct connected component, and let ei and ni be the number of edges
and nodes in the ith-connected component. Then
k k
V (C )  e  n  2 p   ei   ni  2 K
i 1 i 1
k k
  (ei  ni  2)   V (Ci )
i 1 i 1
Software Testing
Two alternate methods are available for the complexity calculations.
1. Cyclomatic complexity V(G) of a flow graph G is equal to the number of

predicate (decision) nodes plus one.
V(G)=  +1
Where  is the number of predicate nodes contained in the flow graph
G.
2. Cyclomatic complexity is equal to the number of regions of the flow

graph.
Software Testing
Example 8.15
Consider a flow graph given in Fig. 23 and calculate the cyclomatic
complexity by all three methods.
Fig. 23
Software Testing
Solution
Cyclomatic complexity can be calculated by any of the three methods.
1. V(G) = e – n + 2P
= 13 – 10 + 2 = 5
2. V(G) =π+1
=4+1=5
3. V(G) = number of regions

=5
Therefore, complexity value of a flow graph in Fig. 23 is 5.
Software Testing
Example 8.16
Consider the previous date program with DD path graph given in Fig. 17.
Find cyclomatic complexity.
Software Testing
Solution
Number of edges (e) = 65

Number of nodes (n) =49
(i) V(G) = e – n + 2P = 65 – 49 + 2 = 18
(ii) V(G) = π + 1 = 17 + 1 = 18
(iii) V(G) = Number of regions = 18
The cyclomatic complexity is 18.
Software Testing
Example 8.17
Consider the quadratic equation problem given in example 8.13 with its DD
Path graph. Find the cyclomatic complexity:
Software Testing
Solution
Number of nodes (n) = 19

(i) V(G) = e – n + 2P = 24 – 19 + 2 = 7
(ii) V(G) = π + 1 = 6 + 1 = 7
Hence cyclomatic complexity is 7 meaning thereby, seven

independent paths in the DD Path graph.
Software Testing
Example 8.18
Consider the classification of triangle problem given in example 8.14. Find

the cyclomatic complexity.
Software Testing
Solution

Number of nodes (n) =18
(i) V(G) = e – n + 2P = 23 – 18 + 2 = 7
(ii) V(G) = π + 1 = 6 + 1 = 7
The cyclomatic complexity is 7. Hence, there are seven independent

paths as given in example 8.14.
Software Testing
Graph Matrices
A graph matrix is a square matrix with one row and one column for every node in the
graph. The size of the matrix (i.e., the number of rows and columns) is equal to the
number of nodes in the flow graph. Some examples of graphs and associated
matrices are shown in fig. 24.
Fig. 24 (a): Flow graph and graph matrices

Software Testing
Fig. 24 (b): Flow graph and graph matrices

Software Testing
Fig. 24 (c): Flow graph and graph matrices

Software Testing
Fig. 25 : Connection matrix of flow graph shown in Fig. 24 (c)

Software Testing
The square matrix represent that there are two path ab and cd from node 1 to
node 2.
Software Testing
Example 8.19
Consider the flow graph shown in the Fig. 26 and draw the graph & connection
matrices. Find out cyclomatic complexity and two / three link paths from a node to
any other node.
Fig. 26 : Flow graph
Software Testing
Solution
The graph & connection matrices are given below :
To find two link paths, we have to generate a square of graph matrix [A] and for three
link paths, a cube of matrix [A] is required.
Software Testing
Software Testing
Data Flow Testing
Data flow testing is another from of structural testing. It has nothing to do with data
flow diagrams.
i. Statements where variables receive values.
ii. Statements where these values are used or referenced.
As we know, variables are defined and referenced throughout the program. We may
have few define/ reference anomalies:
i. A variable is defined but not used/ referenced.
ii. A variable is used but never defined.
iii. A variable is defined twice before it is used.

Software Testing
Definitions
The definitions refer to a program P that has a program graph G(P) and a set of
program variables V. The G(P) has a single entry node and a single exit node. The
set of all paths in P is PATHS(P)
(i) Defining Node: Node n ϵ G(P) is a defining node of the variable v ϵ V,

written as DEF (v, n), if the value of the variable v is defined at the statement
fragment corresponding to node n.
(ii) Usage Node: Node n ϵ G(P) is a usage node of the variable v ϵ V, written as
USE (v, n), if the value of the variable v is used at statement fragment
corresponding to node n. A usage node USE (v, n) is a predicate use (denote
as p) if statement n is a predicate statement otherwise USE (v, n) is a
computation use (denoted as c).
Software Testing
(iii) Definition use: A definition use path with respect to a variable v (denoted
du-path) is a path in PATHS(P) such that, for some v ϵ V, there are define and
usage nodes DEF(v, m) and USE(v, n) such that m and n are initial and final
nodes of the path.
(iv) Definition clear : A definition clear path with respect to a variable v (denoted
dc-path) is a definition use path in PATHS(P) with initial and final nodes DEF (v,
m) and USE (v, n), such that no other node in the path is a defining node of v.
The du-paths and dc-paths describe the flow of data across source statements from
points at which the values are defined to points at which the values are used. The du-
paths that are not definition clear are potential trouble spots.
Software Testing
Hence, our objective is to find all du-paths and then identity those du-paths which are
not dc-paths. The steps are given in Fig. 27. We may like to generate specific test
cases for du-paths that are not dc-paths.
Fig. 27 : Steps for data flow testing

Software Testing
Example 8.20
Consider the program of the determination of the nature of roots of a quadratic

equation. Its input is a triple of positive integers (say a,b,c) and values for each of
these may be from interval [0,100]. The program is given in Fig. 19. The output may
have one of the option given below:
(i) Not a quadratic program
(ii) real roots
(iii) imaginary roots
(iv) equal roots
(v) invalid inputs
Find all du-paths and identify those du-paths that are definition clear.
Software Testing
Solution
Step I: The program flow graph is given in Fig. 19 (a). The variables used in the
program are a,b,c,d, validinput, D.
Step II: DD Path graph is given in Fig. 19(b). The cyclomatic complexity of this graph
is 7 indicating there are seven independent paths.
Step III: Define/use nodes for all variables are given below:
Variable Defined at node Used at node
a 6 11,13,18,20,24,27,28
b 8 11,18,20,24,28
c 10 11,18
d 18 19,22,23,27
D 23, 27 24,28
Validinput 3, 12, 14 17,31
Software Testing
Step IV: The du-paths are identified and are named by their beginning and ending
nodes using Fig. 19 (a).
Variable Path (beginning, end) nodes Definition clear ?
6, 11 Yes
a
6, 13 Yes
6, 18 Yes
6, 20 Yes
6, 24 Yes
6, 27 Yes
6, 28 Yes
8, 11 Yes
b 8, 18 Yes
8, 20 Yes
8, 24 Yes
8, 28 Yes
Software Testing
10, 11 Yes
c
10, 18 Yes
d 18, 19 Yes
18, 22 Yes
18, 23 Yes
18, 27 Yes
D 23, 24 Yes
23, 28 Path not possible
27, 24 Path not possible
27, 28 Yes
3, 17 no
validinput
3, 31 no
12, 17 no
12, 31 no
14, 17 yes
14, 31 yes
Software Testing
Example 8.21
Consider the program given in Fig. 20 for the classification of a triangle. Its
input is a triple of positive integers (say a,b,c) from the interval [1,100]. The
output may be:
[Scalene, Isosceles, Equilateral, Not a triangle, Invalid inputs].
Find all du-paths and identify those du-paths that are definition clear.
Software Testing
Solution
Step I: The program flow graph is given in Fig. 20 (a). The variables used in
the program are a,b,c, valid input.
Step II: DD Path graph is given in Fig. 20(b). The cyclomatic complexity of
this graph is 7 and thus, there are 7 independent paths.
Step III: Define/use nodes for all variables are given below:
Variable Defined at node Used at node

a 6 10, 11, 19, 22
b 7 10, 11, 19, 22
c 9 10, 11, 19, 22
valid input 3, 13, 16 18, 29
Software Testing
Step IV: The du-paths are identified and are named by their beginning and ending
nodes using Fig. 20 (a).
5, 10 Yes
a
5, 11 Yes
5, 19 Yes
5, 22 Yes
7, 10 Yes
b 7, 11 Yes
7, 19 Yes
7, 22 Yes
Software Testing
9, 10 Yes
c
9, 11 Yes
9, 19 Yes
9, 22 Yes
3, 18 no
valid input
3, 29 no
12, 18 no
12, 29 no
16, 18 Yes
16, 29 Yes
Hence total du-paths are 18 out of which four paths are not definition clear
Software Testing
Mutation Testing
Mutation testing is a fault based technique that is similar to fault seeding, except that
mutations to program statements are made in order to determine properties about
test cases. it is basically a fault simulation technique.
Multiple copies of a program are made, and each copy is altered; this altered copy is
called a mutant. Mutants are executed with test data to determine whether the test
data are capable of detecting the change between the original program and the
mutated program.
A mutant that is detected by a test case is termed “killed” and the goal of mutation
procedure is to find a set of test cases that are able to kill groups of mutant
programs.
Software Testing
When we mutate code there needs to be a way of measuring the degree to which the
code has been modified. For example, if the original expression is x+1 and the
mutant for that expression is x+2, that is a lesser change to the original code than a
mutant such as (c*22), where both the operand and the operator are changed. We
may have a ranking scheme, where a first order mutant is a single change to an
expression, a second order mutant is a mutation to a first order mutant, and so on.
High order mutants becomes intractable and thus in practice only low order mutants
are used.
One difficulty associated with whether mutants will be killed is the problem of
reaching the location; if a mutant is not executed, it cannot be killed. Special test
cases are to be designed to reach a mutant. For example, suppose, we have the
code.
Read (a,b,c);
If(a>b) and (b=c) then
x:=a*b*c; (make mutants; m1, m2, m3 …….)
Software Testing
To execute this, input domain must contain a value such that a is greater than b and
b equals c. If input domain does not contain such a value, then all mutants made at
this location should be considered equivalent to the original program, because the
statement x:=a*b*c is dead code (code that cannot be reached during execution). If
we make the mutant x+y for x+1, then we should take care about the value of y
which should not be equal to 1 for designing a test case.
The manner by which a test suite is evaluated (scored) via mutation testing is as
follows: for a specified test suite and a specific set of mutants, there will be three
types of mutants in the code i.e., killed or dead, live, equivalent. The sum of the
number of live, killed, and equivalent mutants will be the total number of mutants
created. The score associated with a test suite T and mutants M is simply.
# killed
 100%
# total  # equivalent
Software Testing
Levels of Testing
There are 3 levels of testing:
i. Unit Testing
ii. Integration Testing
iii. System Testing
Software Testing
Unit Testing
There are number of reasons in support of unit testing than testing the entire product.
1. The size of a single module is small enough that we can locate an error
fairly easily.
2. The module is small enough that we can attempt to test it in some

demonstrably exhaustive fashion.
3. Confusing interactions of multiple errors in widely different parts of the

software are eliminated.
Software Testing
There are problems associated with testing a module in isolation. How do we run a
module without anything to call it, to be called by it or, possibly, to output intermediate
values obtained during execution? One approach is to construct an appropriate
driver routine to call if and, simple stubs to be called by it, and to insert output
statements in it.
Stubs serve to replace modules that are subordinate to (called by) the module to be
tested. A stub or dummy subprogram uses the subordinate module’s interface, may
do minimal data manipulation, prints verification of entry, and returns.
This overhead code, called scaffolding represents effort that is import to testing, but
does not appear in the delivered product as shown in Fig. 29.
Software Testing
Fig. 29 : Scaffolding required testing a program unit (module)

Software Testing
Integration Testing
The purpose of unit testing is to determine that each independent module is

correctly implemented. This gives little chance to determine that the interface
between modules is also correct, and for this reason integration testing must be
performed. One specific target of integration testing is the interface: whether
parameters match on both sides as to type, permissible ranges, meaning and
utilization.
Software Testing
Fig. 30 : Three different integration approaches

Software Testing
System Testing
Of the three levels of testing, the system level is closet to everyday experiences.
We test many things; a used car before we buy it, an on-line cable network
service before we subscribe, and so on. A common pattern in these familiar
forms is that we evaluate a product in terms of our expectations; not with respect
to a specification or a standard. Consequently, goal is not to find faults, but to
demonstrate performance. Because of this we tend to approach system testing
from a functional standpoint rather than from a structural one. Since it is so
intuitively familiar, system testing in practice tends to be less formal than it might
be, and is compounded by the reduced testing interval that usually remains
before a delivery deadline.
Petschenik gives some guidelines for choosing test cases during system testing.
Software Testing
During system testing, we should evaluate a number of attributes of the
software that are vital to the user and are listed in Fig. 31. These represent the
operational correctness of the product and may be part of the software
specifications.
Usable Is the product convenient, clear, and predictable?
Secure Is access to sensitive data restricted to those with authorization?
Will the product work correctly in conjunction with existing data,

Compatible
software, and procedures?
Do adequate safeguards against failure and methods for recovery

Dependable
exist in the product?
Documented Are manuals complete, correct, and understandable?
Fig. 31 : Attributes of software to be tested during system testing

Software Testing
Validation Testing
o It refers to test the software as a complete product.
o This should be done after unit & integration testing.
o Alpha, beta & acceptance testing are nothing but the various ways of involving
customer during testing.
Software Testing
Validation Testing
o IEEE has developed a standard (IEEE standard 1059-1993) entitled “ IEEE guide
for software verification and validation “ to provide specific guidance about
planning and documenting the tasks required by the standard so that the
customer may write an effective plan.
o Validation testing improves the quality of software product in terms of functional
capabilities and quality attributes.
Software Testing
The Art of Debugging
The goal of testing is to identify errors (bugs) in the program. The process of
testing generates symptoms, and a program’s failure is a clear symptom of the
presence of an error. After getting a symptom, we begin to investigate the cause
and place of that error. After identification of place, we examine that portion to
identify the cause of the problem. This process is called debugging.
Debugging Techniques
Pressman explained few characteristics of bugs that provide some clues.
1. “The symptom and the cause may be geographically remote. That is, the
symptom may appear in one part of a program, while the cause may actually be
located in other part. Highly coupled program structures may complicate this
situation.
2. The symptom may disappear (temporarily) when another error is corrected.
Software Testing
3. The symptom may actually be caused by non errors (e.g. round off inaccuracies).
4. The symptom may be caused by a human error that is not easily traced.
5. The symptom may be a result of timing problems rather than processing

problems.
6. It may be difficult to accurately reproduce input conditions (e.g. a real time

application in which input ordering is indeterminate).
7. The symptom may be intermittent. This is particularly common in embedded

system that couple hardware with software inextricably.
8. The symptom may be due to causes that are distributed across a number of tasks
running on different processors”.
Software Testing
Induction approach
 Locate the pertinent data
 Organize the data
 Devise a hypothesis
 Prove the hypothesis
Software Testing
Fig. 32 : The inductive debugging process

Software Testing
Deduction approach
 Enumerate the possible causes or hypotheses
 Use the data to eliminate possible causes
 Refine the remaining hypothesis
 Prove the remaining hypothesis
Software Testing
Fig. 33 : The inductive debugging process
Software Testing
Testing Tools
One way to improve the quality & quantity of testing is to make the process as
pleasant as possible for the tester. This means that tools should be as concise,
powerful & natural as possible.
The two broad categories of software testing tools are :
 Static
 Dynamic
Software Testing
There are different types of tools available and some are listed below:
1. Static analyzers, which examine programs systematically and automatically.
2. Code inspectors, who inspect programs automatically to make sure they adhere
to minimum quality standards.
3. standards enforcers, which impose simple rules on the developer.
4. Coverage analysers, which measure the extent of coverage.
5. Output comparators, used to determine whether the output in a program is

appropriate or not.
Software Testing
6. Test file/ data generators, used to set up test inputs.
7. Test harnesses, used to simplify test operations.
8. Test archiving systems, used to provide documentation about programs.
Multiple Choice Questions
Note: Choose most appropriate answer of the following questions:
8.1 Software testing is:
(a) the process of demonstrating that errors are not present
(b) the process of establishing confidence that a program does what it is supposed
to do
(c) the process of executing a program to show it is working as per specifications
(d) the process of executing a program with the intent of finding errors
8.2 Software mistakes during coding are known as:

(a) failures (b) defects
(c) bugs (d) errors
8.3 Functional testing is known as:
(a) Structural testing (b) Behavior testing
(c) Regression testing (d) None of the above
8.4 For a function of n variables, boundary value analysis yields:
(a) 4n+3 test cases (b) 4n+1 test cases
(c) n+4 test cases (d) None of the above
8.5 For a function of two variables, how many cases will be generated by
robustness testing?
(a) 9 (b) 13
(c) 25 (d) 42
8.6 For a function of n variables robustness testing of boundary value analysis yields:
(a) 4n+1 (b) 4n+3
(c) 6n+1 (d) None of the above
8.7 Regression testing is primarily related to:
(a) Functional testing (b) Data flow testing
(c) Development testing (d) Maintenance testing
8.8 A node with indegree=0 and out degree ≠ 0 is called
(a) Source node (b) Destination node
(c) Transfer node (d) None of the above
8.9 A node with indegree ≠ 0 and out degree=0 is called
(a) Source node (b) Predicate node
(c) Destination node (d) None of the above
8.10 A decision table has
(a) Four portions (b) Three portions
(c) Five portions (d) Two portions
8.11 Beta testing is carried out by

(a) Users (b) Developers
(c) Testers (d) All of the above
8.12 Equivalence class partitioning is related to
(a) Structural testing (b) Blackbox testing
(c) Mutation testing (d) All of the above
8.13 Cause effect graphing techniques is one form of
(a) Maintenance testing (b) Structural testing
(c) Function testing (d) Regression testing
8.14 During validation
(a) Process is checked (b) Product is checked
(c) Developer’s performance is evaluated (d) The customer checks the product
8.15 Verification is
(a) Checking the product with respect to customer’s expectation
(b) Checking the product with respect to specifications
(c) Checking the product with respect to the constraints of the project
(d) All of the above
8.16 Validation is
(a) Checking the product with respect to customer’s expectation
(b) Checking the product with respect to specifications
(c) Checking the product with respect to the constraints of the project
(d) All of the above
8.17 Alpha testing is done by
(a) Customer (b) Tester
(c) Developer (d) All of the above
8.18 Site for Alpha testing is
(a) Software company (b) Installation place
(c) Any where (d) None of the above
8.19 Site for Beta testing is
(a) Software company (b) User’s site
(c) Any where (d) All of the above
8.20 Acceptance testing is done by
(a) Developers (b) Customers
(c) Testers (d) All of the above
8.21 One fault may lead to
(a) One failure (b) No failure
(c) Many failure (d) All of the above
8.22 Test suite is
(a) Set of test cases (b) Set of inputs
(c) Set of outputs (d) None of the above
8.23 Behavioral specification are required for:
(a) Modeling (b) Verification
(c) Validation (d) None of the above
8.24 During the development phase, the following testing approach is not adopted
(a) Unit testing (b) Bottom up testing
(c) Integration testing (d) Acceptance testing
8.25 Which is not a functional testing technique?
(a) Boundary value analysis (b) Decision table
8.26 Decision table are useful for describing situations in which:

(a) An action is taken under varying sets of conditions.
(b) Number of combinations of actions are taken under varying sets of conditions
(c) No action is taken under varying sets of conditions
(d) None of the above
8.27 One weakness of boundary value analysis and equivalence partitioning is
(a) They are not effective
(b) They do not explore combinations of input circumstances
(c) They explore combinations of input circumstances
8.28 In cause effect graphing technique, cause & effect are related to
(a) Input and output (b) Output and input
(c) Destination and source (d) None of the above
8.29 DD path graph is called as
(a) Design to Design Path graph (b) Defect to Defect Path graph
(c) Destination to Destination Path graph (d) Decision to decision Path graph
8.30 An independent path is
(a) Any path through the DD path graph that introduce at least one new set of
processing statements or new conditions
(b) Any path through the DD path graph that introduce at most one new set of
processing statements or new conditions
(c) Any path through the DD path graph that introduce at one and only one new
set of processing statements or new conditions
8.31 Cyclomatic complexity is developed by
(a) B.W.Boehm (b) T.J.McCabe
(c) B.W.Lettlewood (d) Victor Basili
8.32 Cyclomatic complexity is denoted by
(a) V(G)=e-n+2P (b) V(G)= ∏ +1
(c) V(G)=Number of regions of the graph (d) All of the above
8.33 The equation V(G)= ∏ +1 of cyclomatic complexity is applicable only if

every predicate node has
(a) two outgoing edges (b) three or more outgoing edges
(c) no outgoing edges (d) none of the above
8.34 The size of the graph matrix is

(a) Number of edges in the flow graph
(b) Number of nodes in the flow graph
(c) Number of paths in the flow graph
(d) Number of independent paths in the flow graph
8.35 Every node is represented by
(a) One row and one column in graph matrix
(b) Two rows and two columns in graph matrix
(c) One row and two columns in graph matrix
8.36 Cyclomatic complexity is equal to

(a) Number of independent paths (b) Number of paths
(c) Number of edges (d) None of the above
8.37 Data flow testing is related to
(a) Data flow diagrams (b) E-R diagrams
(c) Data dictionaries (d) none of the above
8.38 In data flow testing, objective is to find
(a) All dc-paths that are not du-paths (b) All du-paths
(c) All du-paths that are not dc-paths (d) All dc-paths
8.39 Mutation testing is related to
(a) Fault seeding (b) Functional testing
(c) Fault checking (d) None of the above
8.40 The overhead code required to be written for unit testing is called
(a) Drivers (b) Stubs
(c) Scaffolding (d) None of the above
8.41 Which is not a debugging techniques
(a) Core dumps (b) Traces
(c) Print statements (d) Regression testing
8.42 A break in the working of a system is called
(a) Defect (b) Failure
(c) Fault (d) Error
8.43 Alpha and Beta testing techniques are related to
(a) System testing (b) Unit testing
(c) acceptance testing (d) Integration testing
8.44 Which one is not the verification activity
(a) Reviews (b) Path testing
(c) Walkthrough (d) Acceptance testing
8.45 Testing the software is basically
(a) Verification (b) Validation
(c) Verification and validation (d) None of the above
8.46 Integration testing techniques are
(a) Topdown (b) Bottom up
(c) Sandwich (d) All of the above
8.47 Functionality of a software is tested by
(a) White box testing (b) Black box testing
8.48 Top down approach is used for
(a) Development (b) Identification of faults
(c) Validation (d) Functional testing
8.49 Thread testing is used for testing
(a) Real time systems (b) Object oriented systems
(c) Event driven systems (d) All of the above
8.50 Testing of software with actual data and in the actual environment is called
(a) Alpha testing (b) Beta testing
Exercises
8.1 What is software testing? Discuss the role of software testing during
software life cycle and why is it so difficult?
8.2 Why should we test? Who should do the testing?
8.3 What should we test? Comment on this statement. Illustrate the
importance of testing
8.4 Defined the following terms:
(i) fault (ii) failure
(iii) bug (iv) mistake
8.5 What is the difference between
(i) Alpha testing & beta testing
(ii) Development & regression testing
(iii) Functional & structural testing
8.6 Discuss the limitation of testing. Why do we say that complete testing is
impossible?
Exercises
8.7 Briefly discuss the following
(i) Test case design, Test & Test suite
(ii) Verification & Validation
(iii) Alpha, beta & acceptance testing
8.8 Will exhaustive testing (even if possible for every small programs)
guarantee that the program is 100% correct?
8.9 Why does software fail after it has passed from acceptance testing?
Explain.
8.10 What are various kinds of functional testing? Describe any one in detail.
8.11 What is a software failure? Explain necessary and sufficient conditions
for software failure. Mere presence of faults means software failure. Is it
true? If not, explain through an example, a situation in which a failure
will definitely occur.
8.12 Explain the boundary value analysis testing techniques with the help of
an example.
Exercises
8.13 Consider the program for the determination of next date in a calendar.
Its input is a triple of day, month and year with the following range
1 ≤ month ≤ 12
1 ≤ day ≤ 31
1900 1 ≤ year ≤ 2025
The possible outputs would be Next date or invalid date. Design
boundary value, robust and worst test cases for this programs.
8.14 Discuss the difference between worst test case and adhoc test case
performance evaluation by means of testing. How can we be sure that the
real worst case has actually been observed?
8.15 Describe the equivalence class testing method. Compare this with
boundary value analysis techniques
Exercises
8.16 Consider a program given below for the selection of the largest of
numbers
Exercises
(i) Design the set of test cases using boundary value analysis technique and
equivalence class testing technique.
(ii) Select a set of test cases that will provide 100% statement coverage.
(iii) Develop a decision table for this program.
8.17 Consider a small program and show, why is it practically impossible to
do exhaustive testing?
8.18 Explain the usefulness of decision table during testing. Is it really
effective? Justify your answer.
8.19 Draw the cause effect graph of the program given in exercise 8.16.
8.20 Discuss cause effect graphing technique with an example.
8.21 Determine the boundary value test cases the extended triangle problem
that also considers right angle triangles.
Exercises
8.22 Why does software testing need extensive planning? Explain.
8.23 What is meant by test case design? Discuss its objectives and indicate
the steps involved in test case design.
8.24 Let us consider an example of grading the students in an academic
institution. The grading is done according to the following rules:
Generate test cases using equivalence class testing technique
Exercises
8.25 Consider a program to determine whether a number is ‘odd’ or ‘even’
and print the message
NUMBER IS EVEN
Or
NUMBER IS ODD
The number may be any valid integer.
Design boundary value and equivalence class test cases.
8.26 Admission to a professional course is subject to the following
conditions:
Exercises
If aggregate marks of an eligible candidate are more than 225, he/she will be
eligible for honors course, otherwise he/she will be eligible for pass course.
The program reads the marks in the three subjects and generates the
following outputs:
(a) Not Eligible
(b) Eligible to Pass Course
(c) Eligible to Honors Course
Design test cases using decision table testing technique.
8.27 Draw the flow graph for program of largest of three numbers as shown
in exercise 8.16. Find out all independent paths that will guarantee that
all statements in the program have been tested.
8.28 Explain the significance of independent paths. Is it necessary to look for
a tool for flow graph generation, if program size increases beyond 100
source lines?
8.29 Discuss the structure testing. How is it different form functional testing?
Exercises
8.30 What do you understand by structural testing? Illustrate important
structural testing techniques.
8.31 Discuss the importance of path testing during structural testing.
8.32 What is cyclomatic complexity? Explain with the help of an example.
8.33 Is it reasonable to define “thresholds” for software modules? For
example, is a module acceptable if its V(G) ≤ 10? Justify your answer.
8.34 Explain data flow testing. Consider an example and show all “du” paths.
Also identify those “du” paths that are not “dc” paths.
8.35 Discuss the various steps of data flow testing.
8.36 If we perturb a value, changing the current value of 100 by 1000, what
is the effect of this change? What precautions are required while
designing the test cases?
Exercises
8.37 What is the difference between white and black box testing? Is
determining test cases easier in back or white box testing? Is it correct to
claim that if white box testing is done properly, it will achieve close to
100% path coverage?
8.38 What are the objectives of testing? Why is the psychology of a testing
person important?
8.39 Why does software fail after it has passed all testing phases? Remember,
software, unlike hardware does not wear out with time.
8.40 What is the purpose of integration testing? How is it done?
8.41 Differentiate between integration testing and system testing.
8.42 Is unit testing possible or even desirable in all circumstances? Provide
examples to Justify your answer?
8.43 Peteschenik suggested that a different team than the one that does
integration testing should carry out system testing. What are some good
reasons for this?
Exercises
8.44 Test a program of your choice, and uncover several program errors.
Localise the main route of these errors, and explain how you found the
courses. Did you use the techniques of Table 8? Explain why or why not.
8.45 How can design attributes facilitate debugging?
8.46 List some of the problem that could result from adding debugging
statements to code. Discuss possible solutions to these problems.
8.47 What are various debugging approaches? Discuss them with the help of
examples.
8.48 Researchers and practitioners have proposed several mixed testing
strategies intended to combine advantages of various techniques
discussed in this chapter. Propose your own combination, perhaps also
using some kind of random testing at selected points.
8.49 Design a test set for a spell checker. Then run it on a word processor
having a spell checker, and report on possible inadequacies with respect
to your requirements.
Exercises
8.50 4 GLs represent a major step forward in the development of automatic
program generation. Explain the major advantage & disadvantage in the
use of 4 GLs. What are the cost impact of applications of testing and how
do you justify expenditures for these activities.

Chapter 8 Software Testing-1

Uploaded by

Copyright:

Available Formats

Chapter 8 Software Testing-1

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Chapter 8 Software Testing-1

Uploaded by

Copyright:

Available Formats

Software Engineering (3 rd ed.), By K.

1. Testing is the process of demonstrating that errors are not present.

2. The purpose of testing is to show that a program performs its intended

3. Testing is the process of establishing confidence that a program does

These definitions are incorrect.

A more appropriate definition is:

“Testing is the process of executing a program with

• Why should We Test ?

Although software testing is itself an expensive activity, yet launching of

• Who should Do the Testing ?

• What should We Test ?

We should test the program’s responses to every possible input. It means,

Fig. 1: Control flow graph

When developers make mistakes while coding, we call these mistakes

A fault is the representation of an error, where representation is the mode

A failure occurs when a fault executes. A particular fault may cause

Expected Outputs: Any other observation:

 Verification and Validation

Verification is the process of evaluating a system or component to

Fig. 3: Black box testing

0 100 200 300 400

Consider a program for the determination of the nature of roots of a

Quadratic equation will be of type:

1 6 15 1900 14 June, 1900

7 6 2 1962 1 June, 1962

8 6 30 1962 29 June, 1962

9 6 31 1962 Invalid date

11 2 15 1962 14 February, 1962

Consider a simple program to classify a triangle. Its inputs is a triple of

Test case x y z Expected Output

(200,99), (200,100), (200,101), (200,200), (200,299), (200,300)

0 100 200 300 400

Fig. 8.6: Robustness test cases for two variables x

Test case Inputs Test case Inputs

1 100 100 14 200 299

Consider the program for the determination of nature of roots of a quadratic

2 0 50 50 Not quadratic equation

7 101 50 50 Invalid input

15 0 50 100 Not Quadratic

49 1 100 99 Real Roots

101 100 0 0 Equal Roots

119 100 99 99 Imaginary

Consider the program for the determination of previous date in a calendar as

3 6 15 1901 14 June, 1901

7 6 15 2026 Invalid date (outside range)

16 2 15 1962 14 February, 1962

1 1 1 1900 31 December, 1899

15 1 15 2025 14 January, 2025

32 2 2 1901 1 February, 1901

49 2 31 2024 Invalid date

66 6 30 1900 29 June, 1900

78 11 1 1962 31 October, 1962

83 11 2 1962 1 November, 1962

101 12 1 1900 30 November, 1900

119 12 30 2024 29 December, 2024

Robust test cases are given on next slide.

7 50 50 101 Invalid input

Test Case x y z Expected output

15 1 50 100 Not a triangle

101 100 1 1 Not a triangle