11/Aug/2016

Software Testing
(Verification & Validation )
Nguyễn Đức Mận
mannd@duytan.edu.vn
0904 235 945

©DTU- International School 1

Introduction to
Software Testing

©DTU- International School 11/Aug/2016 2

1
 11/Aug/2016

Course Objectives
• Foundations of software verification and validation
(V&V)
• Mostly a practical perspective
• Emphasis on testing (many kinds)
• Most important V&V technique in practice
• More basic coverage of other aspects
• No emphasis on tools as this will change (quickly)over
time
• But, in the future, you’ll be able to assess how useful a
tool is …

©DTU- International School 11/Aug/2016 3

Student’s Outcome
• At the completion of this course, students will be able
to:
• 1. identify the theoretical and practical issues in
software testing; and
• 2. develop thorough and appropriate test cases for
different levels of testing; and
• 3. identify how software quality assurance
activities fit into overall product development; and
• 4. employ the responsibility in an industry job as a
software test analyst with confidence.

©DTU- International School 11/Aug/2016 4

2
 11/Aug/2016

Examples of Software Failures

• Communications: Loss or corruption of communication media, non
delivery of data.

• Space Applications: Lost lives, launch delays, e.g., European Ariane5

shuttle, 1996:

• From the official disaster report: “Due to a malfunction in the control

software, the rocket veered off its flight path 37 seconds after launch.”

• Defense and Warfare: Misidentification of friend or foe.

• Transportation: Deaths, delays, sudden acceleration, inability to brake.

• Electric Power: Death, injuries, power outages, long-term health hazards

(radiation).
©DTU- International School 11/Aug/2016 5

Examples of Software Failures

• Money Management: Fraud, violation of privacy, shutdown of stock
exchanges and banks, negative interest rates.

• Control of Elections: Wrong results (intentional or nonintentional).

• Control of Jails: Technology-aided escape attempts and successes, failures

in software-controlled locks.

• Law Enforcement: False arrests and imprisonments.

©DTU- International School 11/Aug/2016 6

3
 11/Aug/2016

Examples of Software Failures

©DTU- International School 11/Aug/2016 7

Examples of Software Failures

©DTU- International School 11/Aug/2016 8

4
 11/Aug/2016

Ariane 5 – Lesson learned

• Adequate exception handling and redundancy strategies
(real function of a backup system, degraded modes?)
• Clear, complete, documented specifications (e.g.,
preconditions, post-conditions)
• But perhaps more importantly: usage-based testing (based
on operational profiles), in this case actual Ariane 5
trajectories
• Note this was not a complex, computing problem, but a
deficiency of the software engineering practices in place
…

©DTU- International School 11/Aug/2016 9

F-18 crash
• An F-18 crashed because of a missing exception condition:
• An if ... then ...block without the else clause that was thought
could not possibly arise.
• In simulation, an F-16 program bug caused the virtual plane to
flip over whenever it crossed the equator, as a result of a
missing minus sign to indicate south latitude.

©DTU- International School 11/Aug/2016 10

5
 11/Aug/2016

Fatal Therac-25 Radiation

• Fatal Therac-25 X-ray Radiation
• In 1986, a man in Texas received between 16,500-25,000 radiations in less than 10 sec, over
an area of about 1 cm.
• He passed away 5 months later.
• The root cause of the incident was a SW failure 

• Incident: A patient passed away

• Failure: The device applied higher frequency of radiations than what was safe. Safety range:
[1…10,000 Hz].
• Fault: The software controller of the device did not have a conditional block (if …. else
statements) to perform range checking on the frequency of the radiation to be applied.
• (2) Errors:
• 1.  The SW developer of the device controller system had forgotten to include a range
checking conditional block on the frequency of the radiation to be applied.
• 2.  The device operator was NOT supposed to enter anything outside [1…10,000 Hz]
range.

©DTU- International School 11/Aug/2016 11

Power Shutdown in 2003

©DTU- International School 11/Aug/2016 12

6
 11/Aug/2016

Testing
Definitions & Objectives

©DTU- International School 11/Aug/2016 13

Test Stubs and Drivers

©DTU- International School 11/Aug/2016 14

7
 11/Aug/2016

Summary of Definitions

©DTU- International School 11/Aug/2016 15

The Testing Dilemma

©DTU- International School 11/Aug/2016 16

8
 11/Aug/2016

Testing Process Overview

©DTU- International School 11/Aug/2016 17

Types of Testing
• Functional Testing: testing functional requirements.
• Functional requirements specify specific behavior or
functions of a software.
• Functional testing is thus checking the correct functionality
of a system.
• Non-functional Testing: testing non-functional requirements.
• Non-functional requirements:
• Specify criteria that can be used to judge the operation
of a system, rather than specific behaviors.
• Typical non-functional requirements are performance,
reliability, scalability, and cost.
• Non-functional requirements are often called the –ilities
of a system.

©DTU- International School 11/Aug/2016 18

9
 11/Aug/2016

Fundamental Principles: Exhaustive Testing

• Exhaustive testing, i.e., testing a software system using all
the possible inputs, is most of the time impossible.
• Examples:
• A program that computes the factorial function
(n!=n.(n-1).(n-2)…1)
• Exhaustive testing = running the program with 0, 1, 2,
…, 100, … as an input!
• A compiler (e.g., javac)
• Exhaustive testing = running the (Java) compiler with any
possible (Java) program (i.e., source code)
©DTU- International School 11/Aug/2016 19

Input Equivalence Classes

• General principle to reduce the number of inputs
• Testing criteria group input elements into
(equivalence) classes
• One input in selected in each class (notion of test
coverage)

©DTU- International School 11/Aug/2016 20

10
 11/Aug/2016

Test Coverage

©DTU- International School 11/Aug/2016 21

Complete Coverage: White-Box

©DTU- International School 11/Aug/2016 22

11
 11/Aug/2016

Complete Coverage: Black-Box

• Specification of Compute Factorial Number : If the input value n is
< 0, then an appropriate error message must be printed. If 0 <= n <
20, then the exact value of n! must be printed. If 20 <= n < 200, then
an approximate value of n! must be printed in floating point format,
e.g., using some approximate method of numerical calculus. The
admissible error is 0.1% of the exact value. Finally, if n>=200, the
input can be rejected by printing an appropriate error message.

• Because of expected variations in behavior, it is quite natural to

divide the input domain into the classes {n<0}, {0<= n <20}, {20
<= n < 200}, {n >= 200}. We can use one or more test cases from
each class in each test set. Correct results from one such test set
support the assertion that the program will behave correctly for any
other class value, but there is no guarantee!

©DTU- International School 11/Aug/2016 23

Black vs. White Box Testing

©DTU- International School 11/Aug/2016 24

12
 11/Aug/2016

Black vs. White Box Testing

©DTU- International School 11/Aug/2016 25

Theoretical Foundations of Testing: Formal definitions

©DTU- International School 11/Aug/2016 26

13
 11/Aug/2016

Theoretical Foundations of Testing:

Test Adequacy Criterion

©DTU- International School 11/Aug/2016 27

Test Organization

©DTU- International School 11/Aug/2016 28

14
 11/Aug/2016

Unit testing

©DTU- International School 11/Aug/2016 29

Integration/Interface Testing

©DTU- International School 11/Aug/2016 30

15
 11/Aug/2016

System Testing

©DTU- International School 11/Aug/2016 31

System vs. Acceptance Testing

• System testing
• The software is compared with the requirements
specifications (verification)
• Usually performed by the developers, who know the
system
• Acceptance testing
• The software is compared with the end-user
requirements (validation)
• Usually performed by the customer (buyer), who
knows the environment where the system is to be used
• Sometime distinguished between α - β-testing for
general purpose products

©DTU- International School 11/Aug/2016 32

16
 11/Aug/2016

Testing throughout the LifeCycle

• Much of the life-cycle development artifacts provides a rich
source of test data
• Identifying test requirements and test cases early helps shorten
the development time
• They may help reveal faults
• It may also help identify early low testability specifications or
design

©DTU- International School 11/Aug/2016 33

©DTU- International School 11/Aug/2016 34

17
 11/Aug/2016

©DTU- International School 11/Aug/2016 35

©DTU- International School 11/Aug/2016 36

18
 11/Aug/2016

Types of testing
• One possible classification is based on the following
four classifiers:
• C1: Source of test case generation.
• C2: Lifecycle phase in which testing takes place
• C3: Goal of a specific testing activity
• C4: Characteristics of the artifact under test

©DTU- International School 11/Aug/2016 37

Testing Activities BEFORE Coding

• Testing is a time consuming activity
• Devising a test strategy and identify the test
requirements represent a substantial part of it
• Planning is essential
• Testing activities undergo huge pressure as it is is run
towards the end of the project
• In order to shorten time-to-market and ensure a
certain level of quality, a lot of QA-related activities
(including testing) must take place early in the
development life cycle

©DTU- International School 11/Aug/2016 38

19
 11/Aug/2016

Testing takes creativity

• Many jobs out there in test automation
• To develop an effective test, one must have:
• Detailed understanding of the system
• Knowledge of testing techniques
• Skill to apply these techniques in an effective and
efficient manner
• Testing is done best by independent testers
• Programmer often stick to the data set that makes the
program work
• A program often does not work when tried by somebody
else.

©DTU- International School 11/Aug/2016 39

20