Scribd
Upload
14 views

TNC Examples

Uploaded by

Raheela Nasim
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
14 views

TNC Examples

Uploaded by

Raheela Nasim
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 14

Chapter 2

Examples

Three examples will be used throughout in Chapters 5 through 9 to illustrate the various unit
testing methods: the triangle problem (a venerable example in testing circles); a logically complex
function, NextDate; and an example that typifies MIS applications, known here as the commis-
sion problem. Taken together, these examples raise most of the issues that testing craftspersons
will encounter at the unit level. The discussion of higher levels of testing in Chapters 11 through
17 uses four other examples: a simplified version of an automated teller machine (ATM), known
here as the simple ATM system (SATM); the currency converter, an event-driven application typi-
cal of graphical user interface (GUI) applications; and the windshield wiper control device from
the Saturn™ automobile. The last example, a garage door controller, illustrates some of the issues
of “systems of systems.”
For the purposes of code-based testing, pseudocode implementations of the three unit-level
examples are given in this chapter. System-level descriptions of the SATM system, the currency
converter, the Saturn windshield wiper system, and the garage door controller are given in
Chapters 11 through 17. These applications are modeled with finite-state machines, variations
of event-driven petri nets, selected StateCharts, and with the Universal Modeling Language
(UML).

2.1  Generalized Pseudocode


Pseudocode provides a language-neutral way to express program source code. This version
is loosely based on Visual Basic and has constructs at two levels: unit and program compo-
nents. Units can be interpreted either as traditional components (procedures and functions)
or as object-oriented components (classes and objects). This definition is somewhat informal;
terms such as expression, variable list, and field description are used with no formal defini-
tion. Items in angle brackets indicate language elements that can be used at the identified
positions. Part of the value of any pseudocode is the suppression of unwanted detail; here, we
illustrate this by allowing natural language phrases in place of more formal, complex condi-
tions (see Table 2.1).

15
© 2010 Taylor & Francis Group, LLC
16  ◾  Software Testing

Table 2.1  Generalized Pseudocode


Language Element Generalized Pseudocode Construct

Comment ‘ <text>

Data structure declaration Type <type name>


<list of field descriptions>
End <type name>

Data declaration Dim <variable> As <type>

Assignment statement <variable> = <expression>

Input Input (<variable list>)

Output Output (<variable list>)

Condition <expression> <relational operator> <expression>

Compound condition <Condition> <logical connective>


<Condition>

Sequence statements in sequential order

Simple selection If <condition> Then


  <then clause>
EndIf

Selection If <condition>
  Then <then clause>
  Else <else clause>
EndIf

Multiple selection Case <variable> Of


Case 1: <predicate>
  <Case clause>
…
Case n: <predicate>
  <Case clause>
EndCase

Counter-controlled repetition For <counter> = <start> To <end>


  <loop body>
EndFor

Pretest repetition While <condition>


  <loop body>
EndWhile
(continued)

© 2010 Taylor & Francis Group, LLC


Examples  ◾  17

Table 2.1  Generalized Pseudocode (Continued)


Language Element Generalized Pseudocode Construct

Posttest repetition Do
  <loop body>
Until <condition>

Procedure definition (similarly <procedure name> (Input: <list of variables>;


for functions and o–o methods) Output: <list of variables>)
 <body>
End <procedure name>

Interunit communication Call <procedure name> (<list of variables>;


<list of variables>)

Class/Object definition <name> (<attribute list>; <method list>, <body>)


End <name>

Interunit communication msg <destination object name>.<method name>


(<list of variables>)

Object creation Instantiate <class name>.<object name> (list of attribute


values)

Object destruction Delete <class name>.<object name>

Program Program <program name>


  <unit list>
End<program name>

2.2 The Triangle Problem


The triangle problem is the most widely used example in software testing literature. Some of the
more notable entries in three decades of testing literature are Gruenberger (1973), Brown and
Lipov (1975), Myers (1979), Pressman (1982) and subsequent editions, Clarke and Richardson
(1983, 1984), Chellappa (1987), and Hetzel (1988). There are others, but this list makes the
point.

2.2.1  Problem Statement


Simple version: The triangle program accepts three integers, a, b, and c, as input. These are
taken to be sides of a triangle. The output of the program is the type of triangle determined
by the three sides: Equilateral, Isosceles, Scalene, or NotATriangle. Sometimes, this problem
is extended to include right triangles as a fifth type; we will use this extension in some of the
exercises.
Improved version: The triangle program accepts three integers, a, b, and c, as input. These
are taken to be sides of a triangle. The integers a, b, and c must satisfy the following conditions:

© 2010 Taylor & Francis Group, LLC


18  ◾  Software Testing

c1. 1 ≤ a ≤ 200 c4. a < b + c


c2. 1 ≤ b ≤ 200 c5. b < a + c
c3. 1 ≤ c ≤ 200 c6. c < a + b

The output of the program is the type of triangle determined by the three sides: Equilateral,
Isosceles, Scalene, or NotATriangle. If an input value fails any of conditions c1, c2, or c3, the pro-
gram notes this with an output message, for example, “Value of b is not in the range of permitted
values.” If values of a, b, and c satisfy conditions c4, c5, and c6, one of four mutually exclusive
outputs is given:

1. If all three sides are equal, the program output is Equilateral.


2. If exactly one pair of sides is equal, the program output is Isosceles.
3. If no pair of sides is equal, the program output is Scalene.
4. If any of conditions c4, c5, and c6 is not met, the program output is NotATriangle.

2.2.2 Discussion
Perhaps one of the reasons for the longevity of this example is that it contains clear but complex
logic. It also typifies some of the incomplete definitions that impair communication among cus-
tomers, developers, and testers. The first specification presumes the developers know some details
about triangles, particularly the triangle inequality: the sum of any pair of sides must be strictly
greater than the third side. The upper limit of 200 is both arbitrary and convenient; it will be used
when we develop boundary value test cases in Chapter 5.

2.2.3  Traditional Implementation


The traditional implementation of this grandfather of all examples has a rather FORTRAN-like
style. The flowchart for this implementation appears in Figure 2.1. Figure 2.2 is a flowchart for the
improved version. The flowchart box numbers correspond to comment numbers in the (FORTRAN-
like) pseudocode program given next. (These numbers correspond exactly to those in Pressman
[1982].) This implementation shows its age; a better implementation is given in Section 2.2.4.
The variable “match” is used to record equality among pairs of the sides. A classic intricacy
of the FORTRAN style is connected with the variable “match”: notice that all three tests for the
triangle inequality do not occur. If two sides are equal, say a and c, it is only necessary to compare
a + c with b. (Because b must be greater than zero, a + b must be greater than c because c equals
a.) This observation clearly reduces the number of comparisons that must be made. The efficiency
of this version is obtained at the expense of clarity (and ease of testing). We will find this version
useful later when we discuss infeasible program execution paths. That is the best reason for per-
petuating this version. Notice that six ways are used to reach the NotATriangle box (12.1–12.6),
and three ways are used to reach the Isosceles box (15.1–15.3).

© 2010 Taylor & Francis Group, LLC


Examples  ◾  19

Input a, b, c

Match = 0

1. a = b? Y 2. Match = Match + 1

3. a = c? Y 4. Match = Match + 2

5. b = c? Y 6. Match = Match + 3

7. Match = 0? Y

N
8. a + b ≤ c?
N 13. Match = 1? Y
N

16. Match = 2? Y 17. a + c ≤ b? 14. a + b ≤ c? 9. a + c ≤ b?

Y
N N
Y
Y N Y
18. Match = 3? Y 19. b + c ≤ a? N 10. b + c ≤ a?

N Y
N Y N

20. Equilateral 15. Isosceles 12. Not a triangle 11. Scalene

Figure 2.1  Flowchart for traditional triangle program implementation.

© 2010 Taylor & Francis Group, LLC


20  ◾  Software Testing

Start

Input a, b, c

c1 = 1≤ a ≤ 200

c1? F a invalid
F
T

c2 = 1≤ b ≤ 200

c2? F b invalid

c3 = 1≤ c ≤ 200

c1 AND c2 AND c3? T c3? F c invalid

Output a, b, c

Triangle
inequalities N Not a triangle
all OK?

a = b AND b = c? Y Equilateral

a ≠ b AND a ≠ c AND Y Scalene


b ≠ c?
N
Isosceles End

Figure 2.2  Flowchart for improved triangle program implementation.

The pseudocode for this is given next.


Program triangle1 ‘Fortran-like version
‘
Dim a, b, c, match As INTEGER
‘
Output(“Enter 3 integers which are sides of a triangle”)
Input(a, b, c)

© 2010 Taylor & Francis Group, LLC


Examples  ◾  21

Output(“Side A is”,a)
Output(“Side B is”,b)
Output(“Side C is”,c)
match = 0
If a = b ‘(1)
Then match = match + 1 ‘(2)
EndIf
If a = c ‘(3)
Then match = match + 2 ‘(4)
EndIf
If b = c ‘(5)
Then match = match + 3 ‘(6)
EndIf
If match = 0 ‘(7)
Then If (a + b)≤ c ‘(8)
Then Output(“NotATriangle”) ‘(12.1)
Else If (b + c) ≤ a ‘(9)
Then Output(“NotATriangle”) ‘(12.2)
Else If (a + c) ≤ b ‘(10)
Then Output(“NotATriangle”) ‘(12.3)
Else Output (“Scalene”) ‘(11)
EndIf
EndIf
EndIf
Else If match = 1 ‘(13)
Then If (a + c) ≤ b ‘(14)
Then Output(“NotATriangle”) ‘(12.4)
Else Output (“Isosceles”) ‘(15.1)
EndIf
Else If match=2 ‘(16)
Then If (a + c) ≤ b
Then Output(“NotATriangle”) (12.5)
Else Output (“Isosceles”) ‘(15.2)
EndIf
Else If match = 3 ‘(18)
Then If (b + c) ≤ a ‘(19)
Then Output(“NotATriangle”) ‘(12.6)
Else Output (“Isosceles”) ‘(15.3)
EndIf
Else Output (“Equilateral”) ‘(20)
EndIf
EndIf
EndIf
EndIf
‘
End Triangle1

2.2.4 Structured Implementations
Program triangle2 ‘Structured programming version of simpler specification

Dim a,b,c As Integer


Dim IsATriangle As Boolean

© 2010 Taylor & Francis Group, LLC


22  ◾  Software Testing

‘Step 1: Get Input


Output(“Enter 3 integers which are sides of a triangle”)
Input(a,b,c)
Output(“Side A is”,a)
Output(“Side B is”,b)
Output(“Side C is”,c)
‘Step 2: Is A Triangle?’
If (a < b + c) AND (b < a + c) AND (c < a + b)
Then IsATriangle = True
Else IsATriangle = False
EndIf
‘
‘Step 3: Determine Triangle Type
If IsATriangle
Then If (a = b) AND (b = c)
Then Output (“Equilateral”)
Else If (a ≠ b) AND (a ≠ c) AND (b ≠ c)
Then Output (“Scalene”)
Else Output (“Isosceles”)
EndIf
EndIf
Else Output(“Not a Triangle”)
EndIf
End triangle2

Third version
Program triangle3’
Dim a, b, c As Integer
Dim c1, c2, c3, IsATriangle As Boolean
‘Step 1: Get Input
Do
Output(“Enter 3 integers which are sides of a triangle”)
Input(a, b, c)
c1 = (1 ≤ a) AND (a ≤ 300)
c2 = (1 ≤ b) AND (b ≤ 300)
c3 = (1 ≤ c) AND (c ≤ 300)
If NOT(c1)
Then Output(“Value of a is not in the range of permitted values”)
EndIf
If NOT(c2)
Then Output(“Value of b is not in the range of permitted values”)
EndIf
If NOT(c3)
ThenOutput(“Value of c is not in the range of permitted values”)
EndIf
Until c1 AND c2 AND c3
Output(“Side A is”,a)
Output(“Side B is”,b)
Output(“Side C is”,c)
‘Step 2: Is A Triangle?
If (a < b + c) AND (b < a + c) AND (c < a + b)
Then IsATriangle = True
Else IsATriangle = False

© 2010 Taylor & Francis Group, LLC


Examples  ◾  23

EndIf
‘Step 3: Determine Triangle Type
If IsATriangle
Then If (a = b) AND (b = c)
Then Output (“Equilateral”)
Else If (a ≠ b) AND (a ≠ c) AND (b ≠ c)
Then Output (“Scalene”)
Else Output (“Isosceles”)
EndIf
EndIf
Else Output(“Not a Triangle”)
EndIf
End triangle3

2.3 The NextDate Function


The complexity in the triangle program is due to the relationships between inputs and correct
outputs. We will use the NextDate function to illustrate a different kind of complexity—logical
relationships among the input variables.

2.3.1 Problem Statement


NextDate is a function of three variables: month, date, and year. It returns the date of the day after
the input date. The month, date, and year variables have integer values subject to these conditions
(the year range ending in 2012 is arbitrary, and is from the first edition):

c1. 1 ≤ month ≤ 12
c2. 1 ≤ day ≤ 31
c3. 1812 ≤ year ≤ 2012

As we did with the triangle program, we can make our problem statement more specific. This
entails defining responses for invalid values of the input values for the day, month, and year. We
can also define responses for invalid combinations of inputs, such as June 31 of any year. If any
of conditions c1, c2, or c3 fails, NextDate produces an output indicating the corresponding vari-
able has an out-of-range value—for example, “Value of month not in the range 1...12.” Because
numerous invalid day–month–year combinations exist, NextDate collapses these into one mes-
sage: “Invalid Input Date.”

2.3.2 Discussion
Two sources of complexity exist in the NextDate function: the complexity of the input domain
discussed previously, and the rule that determines when a year is a leap year. A year is 365.2422
days long; therefore, leap years are used for the “extra day” problem. If we declared a leap year
every fourth year, a slight error would occur. The Gregorian calendar (after Pope Gregory) resolves
this by adjusting leap years on century years. Thus, a year is a leap year if it is divisible by 4, unless
it is a century year. Century years are leap years only if they are multiples of 400 (Inglis, 1961);
thus, 1992, 1996, and 2000 are leap years, while the year 1900 is not a leap year. The NextDate

© 2010 Taylor & Francis Group, LLC


24  ◾  Software Testing

function also illustrates a sidelight of software testing. Many times, we find examples of Zipf’s law,
which states that 80% of the activity occurs in 20% of the space. Notice how much of the source
code is devoted to leap year considerations. In the second implementation, notice how much code
is devoted to input value validation.

2.3.3 Implementations

Program NextDate1 ‘Simple version


Dim tomorrowDay,tomorrowMonth,tomorrowYear As Integer
Dim day,month,year As Integer
Output (“Enter today’s date in the form MM DD YYYY”)
Input (month, day, year)
Case month Of
Case 1: month Is 1,3,5,7,8, Or 10: ‘31 day months (except Dec.)
If day < 31
Then tomorrowDay = day + 1
Else
tomorrowDay = 1
tomorrowMonth = month + 1
EndIf
Case 2: month Is 4,6,9, Or 11 ‘30 day months
If day < 30
Then tomorrowDay = day + 1
Else
tomorrowDay = 1
tomorrowMonth = month + 1
EndIf
Case 3: month Is 12: ‘December
If day < 31
Then tomorrowDay = day + 1
Else
tomorrowDay = 1
tomorrowMonth = 1
If year = 2012
Then Output (“2012 is over”)
Else tomorrow.year = year + 1
EndIf
Case 4: month is 2: ‘February
If day < 28
Then tomorrowDay = day + 1
Else
If day = 28
Then If ((year is a leap year)
Then tomorrowDay = 29 ‘leap year
Else ‘not a leap year
tomorrowDay = 1
tomorrowMonth = 3
EndIf
Else If day = 29
Then If ((year is a leap year)
Then tomorrowDay = 1

© 2010 Taylor & Francis Group, LLC


Examples  ◾  25

tomorrowMonth = 3
Else ‘not a leap year
Output(“Cannot have Feb.”, day)
EndIf
EndIf
EndIf
EndIf
EndCase
Output (“Tomorrow’s date is”, tomorrowMonth, tomorrowDay, tomorrowYear)
End NextDate

Program NextDate2 Improved version


‘
Dim tomorrowDay,tomorrowMonth,tomorrowYear As Integer
Dim day,month,year As Integer
Dim c1, c2, c3 As Boolean
‘
Do
Output (“Enter today’s date in the form MM DD YYYY”)
Input (month, day, year)
c1 = (1 ≤ day) AND (day ≤ 31)
c2 = (1 ≤ month) AND (month ≤ 12)
c3 = (1812 ≤ year) AND (year ≤ 2012)
If NOT(c1)
Then Output(“Value of day not in the range 1..31”)
EndIf
If NOT(c2)
Then Output(“Value of month not in the range 1..12”)
EndIf
If NOT(c3)
Then Output(“Value of year not in the range 1812..2012”)
EndIf
Until c1 AND c2 AND c2

Case month Of
Case 1: month Is 1,3,5,7,8, Or 10: ‘31 day months (except Dec.)
If day < 31
Then tomorrowDay = day + 1
Else
tomorrowDay = 1
tomorrowMonth = month + 1
EndIf
Case 2: month Is 4,6,9, Or 11 ‘30 day months
If day < 30
Then tomorrowDay = day + 1
Else
If day = 30
Then tomorrowDay = 1
tomorrowMonth = month + 1
Else Output(“Invalid Input Date”)
EndIf
EndIf
Case 3: month Is 12: ‘December

© 2010 Taylor & Francis Group, LLC


26  ◾  Software Testing

If day < 31
Then tomorrowDay = day + 1
Else
tomorrowDay = 1
tomorrowMonth = 1
If year = 2012
Then Output (“Invalid Input Date”)
Else tomorrow.year = year + 1
EndIf
EndIf
Case 4: month is 2: ‘February
If day < 28
Then tomorrowDay = day + 1
Else
If day = 28
Then
If (year is a leap year)
Then tomorrowDay = 29 ‘leap day
Else ‘not a leap year
tomorrowDay = 1
tomorrowMonth = 3
EndIf
Else
If day = 29
Then
If (year is a leap year)
Then tomorrowDay = 1
tomorrowMonth = 3
Else
If day > 29
Then Output(“Invalid Input Date”)
EndIf
EndIf
EndIf
EndIf
EndIf
EndCase
Output (“Tomorrow’s date is”, tomorrowMonth, tomorrowDay, tomorrowYear)
‘
End NextDate2

2.4 The Commission Problem


Our third example is more typical of commercial computing. It contains a mix of computation
and decision making, so it leads to interesting testing questions. Our main use of this example will
be in our discussion of data flow and slice-based testing.

2.4.1 Problem Statement
A rifle salesperson in the former Arizona Territory sold rifle locks, stocks, and barrels made by a
gunsmith in Missouri. Locks cost $45, stocks cost $30, and barrels cost $25. The salesperson had to

© 2010 Taylor & Francis Group, LLC


Examples  ◾  27

sell at least one lock, one stock, and one barrel (but not necessarily one complete rifle) per month,
and production limits were such that the most the salesperson could sell in a month was 70 locks,
80 stocks, and 90 barrels. After each town visit, the salesperson sent a telegram to the Missouri
gunsmith with the number of locks, stocks, and barrels sold in that town. At the end of a month,
the salesperson sent a very short telegram showing –1 lock sold. The gunsmith then knew the sales
for the month were complete and computed the salesperson’s commission as follows: 10% on sales
up to (and including) $1000, 15% on the next $800, and 20% on any sales in excess of $1800.

2.4.2 Discussion
This example is somewhat contrived to make the arithmetic quickly visible to the reader. It might be
more realistic to consider some other additive function of several variables, such as various calculations
found in filling out a US 1040 income tax form. (We will stay with rifles.) This problem separates into
three distinct pieces: the input data portion, in which we could deal with input data validation (as we
did for the triangle and NextDate programs), the sales calculation, and the commission calculation
portion. This time, we will omit the input data validation portion. We will replicate the telegram
convention with a sentinel-controlled while loop that is typical of MIS data gathering applications.

2.4.3 Implementation

Program Commission (INPUT,OUTPUT)


‘
Dim locks, stocks, barrels As Integer
Dim lockPrice, stockPrice, barrelPrice As Real
Dim totalLocks,totalStocks,totalBarrels As Integer
Dim lockSales, stockSales, barrelSales As Real
Dim sales,commission : REAL
‘
lockPrice = 45.0
stockPrice = 30.0
barrelPrice = 25.0
totalLocks = 0
totalStocks = 0
totalBarrels = 0
‘
Input(locks)
While NOT(locks = -1) ‘Input device uses -1 to indicate end of data
Input(stocks, barrels)
totalLocks = totalLocks + locks
totalStocks = totalStocks + stocks
totalBarrels = totalBarrels + barrels
Input(locks)
EndWhile
‘
Output(“Locks sold:”, totalLocks)
Output(“Stocks sold:”, totalStocks)
Output(“Barrels sold:”, totalBarrels)
‘
lockSales = lockPrice * totalLocks
stockSales = stockPrice * totalStocks

© 2010 Taylor & Francis Group, LLC


28  ◾  Software Testing

barrelSales = barrelPrice * totalBarrels


sales = lockSales + stockSales + barrelSales
Output(“Total sales:”, sales)
‘
If (sales > 1800.0)
Then
commission = 0.10 * 1000.0
commission = commission + 0.15 * 800.0
commission = commission + 0.20 * (sales–1800.0)
Else If (sales > 1000.0)
Then
commission = 0.10 * 1000.0
commission = commission + 0.15*(sales–1000.0)
Else commission = 0.10 * sales
EndIf
EndIf
Output(“Commission is $”,commission)
End Commission

2.5 The SATM System


To better discuss the issues of integration and system testing, we need an example with larger
scope (Figure 2.3).
The ATM described here is minimal, yet it contains an interesting variety of functionality and
interactions that typify the client side of client–server systems.

Welcome to

Rock Solid Federal Credit Union

Please insert your ATM card

Printed receipt 1 2 3 Card slot

4 5 6 Enter

7 8 9 Clear

0 Cancel

Cash dispenser Deposit slot

Figure 2.3  SATM terminal.

© 2010 Taylor & Francis Group, LLC

You might also like