Lecture 05 Software Testing and Inspection
Lecture 05 Software Testing and Inspection
Lecture 05 Software Testing and Inspection
ENGINEERING II
COURSE CONTENT
• SDLC
Design Patterns
× Software Testing
1. Software Maintenance/Evolution
• Advance Software Engineering
1. Software Reuse
2. Component-Based Software Engineering
3. Distributed Software Engineering
• Others
1. Information Security
2. XML & Data Representation
OUTLINE
• Development Testing
• Program testing goals
• Verification vs validation Brainstorming
• Software inspections
• Inspection & Testing
PROGRAM TESTING
• Testing is used to show that a program does what it is
intended to do and to discover program defects
before using.
• When you test software, you execute a program using
artificial data.
• You check the results of the test run for errors,
anomalies or information about the program’s non-
functional attributes.
• Can reveal the presence of errors NOT their absence.
• Testing is part of a more general verification and
validation process, which also includes static validation
techniques.
VERIFICATION VS VALIDATION
• Testing is part of a broader process of software
verification and validation (V & V).
• Verification and validation are not the same thing,
although they are often confused.
• Verification: "Are we building the product right”.
• The software should conform to its specification.
• Validation: "Are we building the right product”.
• The software should do what the user really requires.
CONT.
• Software verification is the process of checking that the
software meets its stated functional and non-functional
requirements.
• Validation is a more general process. The aim of
software validation is to ensure that the software meets
the customer’s expectations.
V & V CONFIDENCE
• Aim of V & V is to establish confidence that the system
is ‘fit for purpose’.
• Depends on system’s purpose, user expectations and
marketing environment
• Software purpose
• The level of confidence depends on how critical the
software is to an organization.
• User expectations
• Users may have low expectations of certain kinds of
software.
• Marketing environment
• Getting a product to market early may be more important
than finding defects in the program.
SOFTWARE INSPECTION
• As well as software testing, the verification and
validation process may involve software inspections
and reviews.
• Inspections and reviews analyze and check the system
requirements, design models, the program source
code, and even proposed system tests.
• Inspections mostly focus on the source code of a
system, but any readable representation of the
software, such as its requirements or a design model,
can be inspected.
SOFTWARE INSPECTIONS
• These involve people examining the source
representation with the aim of discovering anomalies
and defects.
• Inspections not require execution of a system so may
be used before implementation.
• They may be applied to any representation of the
system (requirements, design, configuration data, test
data, etc.).
• They have been shown to be an effective technique
for discovering program errors.
ADVANTAGES OF INSPECTIONS
• During testing, errors can mask (hide) other errors.
Because inspection is a static process, you don’t have
to be concerned with interactions between errors.
• Incomplete versions of a system can be inspected
without additional costs. If a program is incomplete,
then you need to develop specialized test harnesses to
test the parts that are available.
• As well as searching for program defects, an inspection
can also consider broader quality attributes of a
program, such as compliance with standards,
portability and maintainability.
STAGES OF TESTING
• Development testing, where the system is tested during
development to discover bugs and defects.
• Release testing, where a separate testing team test a
complete version of the system before it is released to
users.
• User testing, where users or potential users of a system
test the system in their own environment.