Core Testing Techniques of Software

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 1
Outline

 Terminology  System testing

 Types of errors  Function testing
  Structure Testing
Dealing with errors
 Performance testing
 Quality assurance vs Testing  Acceptance testing
 Component Testing  Installation testing
 Unit testing
 Integration testing
 Testing Strategy
 Design Patterns & Testing

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 2
Some Observations
 It is impossible to completely test any nontrivial module or any
system
 Theoretical limitations: Halting problem ??
 Practial limitations: Prohibitive in time and cost
 Testing can only show the presence of bugs, not their absence
(Dijkstra)

total number of execution paths?

loop 200 times

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 3
 Testing Activities
Subsystem Requirements
Unit System
Code Test Analysis
Design Document
Tested Document User
Subsystem
Subsystem Manual
Unit
Code Test
Tested Integration Functional
Subsystem
Test Test
Integrated Functioning
Subsystems System

Tested Subsystem

Subsystem Unit
Code Test
All
Alltests
testsby
bydeveloper
developer
Cf. levels of testing

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 4
 Testing Activities continued
Client’s
Global Understanding User
Requirements of Requirements Environment

Functioning Validated Accepted

System PerformanceSystem System
Acceptance Installation
Test Test Test

Usable
Tests
Testsby
byclient
client System
Tests
Testsby
bydeveloper
developer
User’s understanding
System in
Use
Tests
Tests(?)
(?) by
byuser
user
Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 5
Level of abstraction
Levels of Testing in V Model

system system
requireme integration
nts
software
requireme acceptance
nts test

preliminar software

te
y integratio
an

t s
design n
aly

and
componen
z

detailed
ea

i
t

nt
design
nd

test

eg
r
de

at
code & unit
sig

e
debug test
n

Time
N.B.: component test vs. unit
Bernd Bruegge & Allen H. Dutoit
test; acceptance test vs. system integration
Object-Oriented Software Engineering: Using UML, Patterns, and Java 6
 Test Planning [Pressman]

 A Test Plan:  A test plan includes:

 covers all types and phases of  test objectives
testing  schedule and logistics
 guides the entire testing process  test strategies
 who, why, when, what  test cases
 developed as requirements,  procedure
functional specification, and high-  data
level design are developed
 expected result
 should be done before
 procedures for handling
implementation starts
problems

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 7
Fault Handling Techniques
Fault Handling

Fault Tolerance
Fault Avoidance Fault Detection

Design Atomic Modular

Reviews
Methodology Transactions Redundancy

Configuration
Verification
Management

Testing Debugging

Unit Integration System Correctness Performance

Testing Testing Testing Debugging Debugging

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 8
Quality Assurance encompasses Testing
Quality Assurance

Usability Testing

Scenario Prototype Product

Testing Testing Testing

Fault Avoidance Fault Tolerance

Atomic Modular
Configuration Transactions Redundancy
Verification
Management
Fault Detection

Reviews

Debugging
Walkthrough Inspection
Testing

Correctness Performance
Unit Integration System Debugging Debugging
Testing Testing Testing
Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 9
Types of Testing
 Unit Testing:
 Individual subsystem
 Carried out by developers
 Goal: Confirm that subsystems is correctly coded and carries out the
intended functionality
 Integration Testing:
 Groups of subsystems (collection of classes) and eventually the entire
system
 Carried out by developers
 Goal: Test the interface among the subsystem

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 10
System Testing
Terminology:
 System Testing: system testing here = validation testing
 The entire system
 Carried out by developers
 Goal: Determine if the system meets the requirements (functional
and global)
 Acceptance Testing: 2 kinds of Acceptance testing
 Evaluates the system delivered by developers
 Carried out by the client. May involve executing typical
transactions on site on a trial basis
 Goal: Demonstrate that the system meets customer requirements
and is ready to use

 Implementation (Coding) and testing go hand in hand

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 11
 Unit Testing
 Informal:
 Incremental coding Write a little, test a little
 Static Analysis:
 Hand execution: Reading the source code
 Walk-Through (informal presentation to others)
 Code Inspection (formal presentation to others)
 Automated Tools checking for
 syntactic and semantic errors
 departure from coding standards
 Dynamic Analysis:
 Black-box testing (Test the input/output behavior)
 White-box testing (Test the internal logic of the subsystem or object)
 Data-structure based testing (Data types determine test cases)

Which is more effective, static or dynamic analysis?

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 12
Black-box Testing

 Focus: I/O behavior. If for any given input, we can predict the
output, then the module passes the test.
 Almost always impossible to generate all possible inputs ("test
cases") why?
 Goal: Reduce number of test cases by equivalence partitioning:
 Divide input conditions into equivalence classes
 Choose test cases for each equivalence class. (Example: If an object
is supposed to accept a negative number, testing one negative
number is enough)

 If x = 3 then …

 If x > -5 and x < 5 then …

What would be the equivalence classes?

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 13
 Black-box Testing (Continued)
 Selection of equivalence classes (No rules, only guidelines):
 Input is valid across range of values. Select test cases from 3
equivalence classes:
 Below the range
Are these complete?
 Within the range
 Above the range
 Input is valid if it is from a discrete set. Select test cases from 2
equivalence classes:
 Valid discrete value
 Invalid discrete value
 Another solution to select only a limited amount of test cases:
 Get knowledge about the inner workings of the unit being tested =>
white-box testing

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 14
White-box Testing
 Focus: Thoroughness (Coverage). Every statement in the component is executed at
least once.
 Four types of white-box testing
 Statement Testing
 Loop Testing
 Path Testing
 Branch Testing

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 15
White-box Testing (Continued)
 Statement Testing (Algebraic Testing): Test single statements
 Loop Testing:
 Cause execution of the loop to be skipped completely. (Exception:
Repeat loops)
 Loop to be executed exactly once
 Loop to be executed more than once
 Path testing:
 Make sure all paths in the program are executed
 Branch Testing (Conditional Testing): Make sure that each
possible outcome from a condition is tested at least once

if ( i = TRUE) printf("YES\n");else printf("NO\n");

Test cases: 1) i = TRUE; 2) i = FALSE

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 16
White-Box Testing
Loop Testing
[Pressman]

Simple
loop
Nested
Loops

Concatenated
Loops Unstructured
Loops
Why is loop testing important?
Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 17
White-box Testing Example
FindMean(float Mean, FILE ScoreFile)
{ SumOfScores = 0.0; NumberOfScores = 0; Mean = 0;
Read(ScoreFile, Score); /*Read in and sum the scores*/
while (! EOF(ScoreFile) {
if ( Score > 0.0 ) {
SumOfScores = SumOfScores + Score;
NumberOfScores++;
}
Read(ScoreFile, Score);
}
/* Compute the mean and print the result */
if (NumberOfScores > 0 ) {
Mean = SumOfScores/NumberOfScores;
printf("The mean score is %f \n", Mean);
} else
printf("No scores found in file\n");
}
Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 18
White-box Testing Example: Determining the Paths
FindMean (FILE ScoreFile)
{ float SumOfScores = 0.0;
int NumberOfScores = 0;
1
float Mean=0.0; float Score;
Read(ScoreFile, Score);
2 while (! EOF(ScoreFile) {
3 if (Score > 0.0 ) {
SumOfScores = SumOfScores + Score;
4
NumberOfScores++;
}
5
Read(ScoreFile, Score); 6
}
/* Compute the mean and print the result */
7 if (NumberOfScores > 0) {
Mean = SumOfScores / NumberOfScores;
printf(“ The mean score is %f\n”, Mean); 8
} else
printf (“No scores found in file\n”); 9
}

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 19
Constructing the Logic Flow Diagram
Start

F
2
T
3
T F
4 5

7
T F
8 9

Exit

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 20
Finding the Test Cases
Start

1
a (Covered by any data)
2
b (Data set must contain at least one value)
(Positive score) d 3
e (Negative score)
c 4 5
(Data set must h (Reached if either f or
be empty) f g
6 e is reached)

7
(Total score < 0.0) i j (Total score > 0.0)
8 9
k l
Exit

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 21
 Self reading
Comparison of White & Black-box Testing 25.1.2002

 White-box Testing:  Both types of testing are needed

 Potentially infinite number of  White-box testing and black box
paths have to be tested testing are the extreme ends of a
 White-box testing often tests testing continuum.
what is done, instead of what 
should be done
Any choice of test case lies in
between and depends on the
 Cannot detect missing use cases
following:
 Black-box Testing:  Number of possible logical paths
 Potential combinatorical  Nature of input data
explosion of test cases (valid &
 Amount of computation
invalid data)
 Often not clear whether the  Complexity of algorithms and
selected test cases uncover a data structures
particular error
 Does not discover extraneous
use cases ("features")

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 22
 The 4 Testing Steps

1.1.Select
Selectwhat
whathas
hasto
tobe
be 3.3.Develop
Developtest
testcases
cases
measured
measured AAtest
testcase
caseisisaaset
setof
oftest
test
Analysis: data
dataororsituations
situationsthat
thatwill
Analysis:Completeness
Completenessof of will
requirements be
beused
usedtotoexercise
exercisethetheunit
unit
requirements
Design: (code,
(code,module,
module,system)
system)being
being
Design:tested
testedfor
forcohesion
cohesion tested
testedororabout
aboutthe theattribute
attribute
Implementation:
Implementation:Code
Codetests being
tests beingmeasured
measured
2.2.Decide
Decidehow
howthe
thetesting
testingisis 4.4.Create
Createthe
thetest
testoracle
oracle
done
done An
Anoracle
oraclecontains
containsofofthe
the
Code
Codeinspection
inspection predicted
predictedresults
resultsfor
foraaset
setof
of
Proofs test
testcases
cases
Proofs(Design
(DesignbybyContract)
Contract)
Black-box, The
Thetest
testoracle
oraclehas
hasto
tobe
be
Black-box,white
whitebox,
box, written down before the
Select written down before the
Selectintegration
integrationtesting
testing actual
actualtesting
testingtakes
takesplace
place
strategy
strategy(big
(bigbang,
bang,bottom
bottom
up,
up,top
topdown,
down,sandwich)
sandwich)
Next module
Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 23
 Self reading
Guidance for Test Case Selection
 Use
Useanalysis
analysis knowledge
knowledge  Use
Useimplementation
implementation
about
aboutfunctional
functional knowledge
requirements knowledgeabout
aboutalgorithms:
algorithms:
requirements(black-box
(black-box Examples:
testing):
testing): Examples:
Use Force
Forcedivision
divisionby
byzero
zero
Usecases
cases
Expected Use
Usesequence
sequenceofoftest
testcases
casesfor
Expectedinput
inputdata
data for
Invalid interrupt
interrupthandler
handler
Invalidinput
inputdata
data
 Use
Usedesign
design knowledge
knowledgeabout
about
system
systemstructure,
structure,algorithms,
algorithms,
data
datastructures
structures (white-box
(white-box
testing):
testing):
Control
Controlstructures
structures

 Test
Testbranches,
branches,loops,
loops,......
Data
Datastructures
structures

 Test
Testrecords
recordsfields,
fields,
arrays, ...
arrays, ...

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 24
 Self reading
Unit-testing Heuristics

1.1.Create
Createunit
unittests
testsasassoon
soonasasobject
object 4.4.Desk
Deskcheck
checkyour
yoursource
sourcecode
code
design
designisiscompleted:
completed: Reduces
Reducestesting
testingtime
time
Black-box
Black-boxtest:test:Test
Testthe
theuse
use 5.5.Create
Createaatest
testharness
harness
cases & functional model Test
cases & functional model Testdrivers
driversandandtest
teststubs
stubsareare
White-box needed
neededforforintegration
integrationtesting
White-boxtest: test:Test
Testthe
the testing
dynamic
dynamicmodel model 6.6.Describe
Describethethetest
testoracle
oracle
Data-structure Often
Oftenthetheresult
resultof ofthe
thefirst
Data-structuretest: test:Test
Testthethe first
object
objectmodel
model successfully executed
successfully executed test test
2.2.Develop 7.7.Execute
Executethe
thetest
testcases
cases
Developthe thetest
testcases
cases
Goal: Don’t
Don’tforget
forgetregression
regressiontesting
testing
Goal:Find
Findthe theminimal
minimal Re-execute
number
numberof oftest
testcases
casestotocover
cover Re-executetest testcases
casesevery
everytime
time
as aachange
changeisismade.
asmany
manypathspathsas aspossible
possible made.
Big cost -> what should be done?
3.3.Cross-check
Cross-checkthe thetest
testcases
casestoto
eliminate 8.8.Compare
Comparethe theresults
resultsof
ofthe
thetest
testwith
withthe
eliminateduplicates
duplicates test oracle
the
Don't test oracle
Don'twaste
wasteyouryourtime!
time! Automate
Automateas asmuch
muchas aspossible
possible
Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 25
 OOT Strategy
[Pressman]

 class testing is the equivalent of unit testing

…if there is no nesting of classes
 operations within the class are tested
 the state behavior of the class is examined

 integration applied three different strategies/levels of

abstraction
 thread-based testing—integrates the set of classes required
to respond to one input or event
 use-based testing—integrates the set of classes required to
respond to one use case
…this is pushing…
 cluster testing—integrates the set of classes required to
demonstrate one collaboration

Recall: model-driven software development

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 26
 OOT—Test Case Design
[Pressman]

Berard [BER93] proposes the following approach:

1. Each test case should be uniquely identified and should be explicitly

associated with the class to be tested,
2. A list of testing steps should be developed for each test and should
contain [BER94]:
a. a list of specified states for the object that is to be tested
b. a list of messages and operations that will be exercised as a
consequence of the test how can this be done?
c. a list of exceptions that may occur as the object is tested
d. a list of external conditions (i.e., changes in the environment external
to the software that must exist in order to properly conduct the test)

{people, machine, time of operation, etc.}

This is a kind of data structure testing

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 27
 OOT Methods: Behavior Testing [Pressman]

The tests to be empty set up

designed should open acct setup Accnt acct
achieve all state
coverage [KIR94]. deposit
(initial)
That is, the
operation deposit

sequences should working

cause the Account balance
acct
withdraw
class to make credit
accntInfo
transition through
withdrawal
all allowable states (final)

dead nonworking
acct close acct

Figure 14.3 State diagram for Account class (adapted from [ KIR94])

This can act as an oracle

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 28
 Who Tests the Software?
[Pressman]

developer independent tester

Understands the system Must learn about the system,
but, will test "gently" but, will attempt to break it
and, is driven by "delivery" and, is driven by quality

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 29
 NFRs: Reliability [Chung, RE Lecture Notes]]

Counting Bugs
 Sometimes reliability requirements take the form:
"The software shall have no more than X bugs/1K LOC"
But how do we measure bugs at delivery time?

 Bebugging Process - based on a Monte Carlo technique for statistical analysis of random events.
1. before testing, a known number of bugs (seeded bugs) are secretly inserted.
2. estimate the number of bugs in the system
3. remove (both known and new) bugs.

# of detected seeded bugs/ # of seeded bugs = # of detected bugs/ # of bugs in the system
# of bugs in the system = # of seeded bugs x # of detected bugs /# of detected seeded bugs

Example: secretely seed 10 bugs

an independent test team detects 120 bugs (6 for the seeded)
# of bugs in the system = 10 x 120/6 = 200
# of bugs in the system after removal = 200 - 120 - 4 = 76

 But, deadly bugs vs. insignifant ones; not all bugs are equally detectable; ( Suggestion [Musa87]:

"No more than X bugs/1K LOC may be detected during testing"

"No more than X bugs/1K LOC may be remain after delivery,
as calculated by the Monte Carlo seeding technique"
Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 30
Summary

 Testing
Testingisisstill
stillaablack
blackart,
art,but
butmany
manyrules
rulesand
andheuristics
heuristicsare
are
available
available
 Testing consists of component-testing (unit testing, integration
Testing consists of component-testing (unit testing, integration
testing)
testing)and
andsystem
systemtesting,
testing,and
and…
…
 OOT and architectural testing, still challenging
OOT and architectural testing, still challenging
 User-oriented reliability modeling and evaluation not adequate
User-oriented reliability modeling and evaluation not adequate
 Testing has its own lifecycle
Testing has its own lifecycle

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 31
Additional Slides

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 32
 Terminology

 Reliability: The measure of success with which the observed

behavior of a system confirms to some specification of its
behavior.
 Failure: Any deviation of the observed behavior from the
specified behavior.
 Error: The system is in a state such that further processing by
the system will lead to a failure.
 Fault (Bug): The mechanical or algorithmic cause of an error.

There are many different types of errors and different ways how
we can deal with them.

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 33
Examples of Faults and Errors

 Faults 
Faultsin
inthe
theInterface
Interface Mechanical
MechanicalFaults
Faults(very
(very
specification
specification hard
hardto
tofind)
find)
Mismatch
Mismatchbetween
betweenwhat
whatthe
the Documentation
Documentationdoes
doesnot
not
client
clientneeds
needsand
andwhat
whatthe
the match
match actual
actualconditions
conditionsor
or
server
serveroffers
offers operating
operatingprocedures
procedures
Mismatch
Mismatchbetween
between  Errors
requirements
Errors
requirementsandand Stress
implementation
implementation Stressor
oroverload
overloaderrors
errors
Capacity
Capacityororboundary
boundaryerrors
errors
 Algorithmic
AlgorithmicFaults
Faults Timing
Missing Timingerrors
errors
Missinginitialization
initialization Throughput
Branching Throughputor orperformance
performance
Branchingerrors
errors(too
(toosoon,
soon, errors
errors
too
toolate)
late)
Missing
Missingtest
testfor
fornil
nil

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 34
 Dealing with Errors
 Verification:
 Assumes hypothetical environment that does not match real
environment
 Proof might be buggy (omits important constraints; simply wrong)
 Modular redundancy:
 Expensive
 Declaring a bug to be a “feature”
 Bad practice
 Patching
 Slows down performance
 Testing (this lecture)
 Testing is never good enough

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 35
 Another View on How to Deal with Errors
 Error prevention (before the system is released):
 Use good programming methodology to reduce complexity
 Use version control to prevent inconsistent system
 Apply verification to prevent algorithmic bugs
 Error detection (while system is running):
 Testing: Create failures in a planned way
 Debugging: Start with an unplanned failures
 Monitoring: Deliver information about state. Find performance bugs
 Error recovery (recover from failure once the system is released):
 Data base systems (atomic transactions)
 Modular redundancy
 Recovery blocks

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 36
What is this?

A failure?

An error?

A fault?
Need to specify
the desired behavior first!

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 37
Erroneous State (“Error”)

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 38
Algorithmic Fault

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 39
Mechanical Fault

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 40
 How do we deal with Errors and Faults?

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 41
Verification?

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 42
Modular Redundancy?

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 43
Declaring the Bug
as a Feature?

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 44
Patching?

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 45
Testing?

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 46
Testing takes creativity

 Testing often viewed as dirty work.

 To develop an effective test, one must have:
 Detailed understanding of the system
 Knowledge of the testing techniques
 Skill to apply these techniques in an effective and efficient manner
 Testing is done best by independent testers
 We often develop a certain mental attitude that the program should
in a certain way when in fact it does not.
 Programmer often stick to the data set that makes the program
work
 "Don’t mess up my code!"
 A program often does not work when tried by somebody else.
 Don't let this be the end-user.

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 47
Test Cases

 Test case 1 : ? (To execute loop exactly once)

 Test case 2 : ? (To skip loop body)
 Test case 3: ?,? (to execute loop more than once)

 These 3 test cases cover all control flow paths

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 48