Lecture5 Part1 IT309

IT-309 SYSTEMS INTEGRATION & ARCHITECTURE 1
Lecturer :
Engr. Evangeline F. Gonzales
Associate Professor III
Lecture 5- Testing Life Cycle &Techniques
01 Testing Techniques
02 Testing Administration
What are the different testing techniques?
SOFTWARE DEVELOPMENT MODELS
What are the different software development models?
Terms:
● Commercial Off-The -Shelf (COTS)
● Iterative-incremental development model
● Validation
● Verification
● V-model
Software Development Models

● Providing guidance on the order in which a
project should carry out its major tasks and
criteria for transitioning between stages
● Different
development
life cycle models
need different
approaches to
testing

● Software development models, like test
strategies, must be adapted to the context
of the project and to the product
characteristics
V-Model (Sequential Development Model)

A V-model may have
more, fewer or different
levels of development
and testing depending
on the project and the
software product.
Iterative-Incremental Development Model

Iterative LC - Regression Testing

Testing (including Regression Test) increases
at each iteration. Regression Testing is
increasingly important on all iterations after the
first one.
COTS-Oriented Life Cycle

Testing within a Life Cycle Model (V-Model)

Exercise 1
An incremental lifecycle model is being used to develop a
new application. Which of the following statements about the
required testing is MOST likely to be CORRECT?
A. Acceptance tests for all increments should be designed before any
development iterations begin
B. User acceptance testing will be performed only once all the increments have
been completed
C. Regression testing is going to become increasingly important as each
increment is developed
D. On each iteration, a single test activity of regression testing will need to be
performed
Exercise 2
A V-model is being used as the software development model
on a project developing a financial messaging system. The
system will need to communicate with several existing
systems. Which of the following test levels is MOST likely to
be used as part of the model?
A. Operational Integration Testing
B. System Integration Testing
C. Regulation Maintenance Testing
D. Contract System Testing
Exercise 3
Which of the following is a characteristic of good testing that is applicable
to any lifecycle model?
A. Testers should participate in reviewing documents as soon as they
are approved
B. Test design should begin immediately after the corresponding
development activity has ended
C. Each test level on a project shares the same test objectives
D. For every development activity, there is a corresponding test activity
How to administer tests?
Test Levels
Terms:
Alpha testing
●
Beta testing
●
Component testing
●
Driver
●
Field testing
●
● Functional requirement
● Integration
● Integration testing
● Non-functional requirement
● Robustness testing
● Stub
● System testing
● Test environment
● Test level
● Test-driven development
● User acceptance testing
For each test levels, the following can be

identified:
● Generic Objectives
● Work product(s) being referenced for

deriving test cases (i.e. test basis)
● Test Object (i.e. what is being tested)
● Typical defects and failures to be found

● Test harness requirements and tool support

● Specific approaches and responsibilities
Component Testing
Test basis:
● Component requirements
● Detailed design
● Code
TEST ADMINISTRATION
Typical test objects:

● Components
● Programs
● Data conversion / migration programs
● Data base modules
TEST ADMINISTRATION
Objectives of Component Testing

● Testing functionality
● Testing non-functional characteristics (e.g.
memory leaks)
● Testing robustness
● Verifying error tolerance
TEST ADMINISTRATION
Objectives of Component
Testing
● Verifying interfaces
within a module
● Verifying local data,
boundary values
TEST ADMINISTRATION
Integration Testing
Test basis:
● Software and system design
● Architecture
● Workflows
● Use cases
TEST ADMINISTRATION

● Subsystems
● Database implementation
● Infrastructure
● Interfaces
● System configuration and configuration data

TEST ADMINISTRATION
Objectives of Integration Testing

● Assembling tested components into a single
system
● Tests interfaces and combinations of
interacting components
TEST ADMINISTRATION
● There may be more than one level of

integration testing
○ Component Integration Testing
■ Tests the interactions between

software components and is done after
component testing
TEST ADMINISTRATION
○ System Integration Testing

■ Tests the interactions between
different systems or between hardware
and software and may be done after
system testing
TEST ADMINISTRATION
System Testing
Test basis:
● System and software requirement
specification
● Use cases
● Functional specification
● Risk analysis reports

TEST ADMINISTRATION

● System, user and operation manuals
● System configuration and configuration data
Objectives of System Testing

● Verifying the behavior of a whole system or
application
TEST ADMINISTRATION
● The test environment should correspond to

the final production environment as much as
possible to minimize the risk of environment
-specific failures
● Investigate both functional and
nonfunctional requirement of system and
data quality characteristics
TEST ADMINISTRATION
● Effective System Testing needs to be

executed without unit or integration defects
● Testers also need to deal with incomplete or
undocumented requirements
● An independent test team often carries out
system testing
TEST ADMINISTRATION
Acceptance Testing
Test basis:
● User requirements
● System requirements
● Use Cases
● Business processes
● Risk analysis reports

TEST ADMINISTRATION

● Business processes on fully integrated
system
● Operational and maintenance processes
● User procedures
● Forms
● Reports
● Configuration data
TEST ADMINISTRATION
Objectives of Accepance Testing

● It is often the responsibility of the customers
or users of a system; other stakeholders

may be involved as well.
● Goal: To establish confidence in the system,
parts of the system or specific non-functional

characteristics of the system.
TEST ADMINISTRATION
● Finding defects is not the main focus in

acceptance testing
● Acceptance testing is not necessarily the
final level of testing
○ E.g. a large-scale system integration test
may come after the acceptance test for a

system.
TEST ADMINISTRATION
● Acceptance testing may occur at various

times in the life cycle, for example:
○ A COTS software product may be
acceptance tested when it is installed or
integrated
TEST ADMINISTRATION
○ Acceptance testing of the usability of a

component may be done during
component testing
○ Acceptance testing of a new functional
enhancement may come before system
testing
TEST ADMINISTRATION
Forms of Acceptance Testing

● User acceptance testing
○ fitness for use of the system by business
users.
● Operational (acceptance) testing
○ Testing of backup/restore
○ Disaster recovery
TEST ADMINISTRATION
● Operational (acceptance) testing

○ User management
○ Maintenance tasks
○ Data load and migration task
○ Periodic checks of security vulnerabilities

TEST ADMINISTRATION
Forms of Acceptance Testing

● Contract and regulation acceptance testing
○ Contract acceptance testing is

performed against a contract’s acceptance
criteria for producing custom-developed
software.
TEST ADMINISTRATION
○ Acceptance criteria should be defined

when the parties agree to the contract .
○ Regulation acceptance testing is
performed against any regulations that
must be adhered to, such as government,
legal or safety regulations.
TEST ADMINISTRATION
● Alpha and beta (or field) testing

○ Alpha testing is performed at the
developing organization’s site but not by
the developing team.
○ Beta testing, or field-testing, is
performed by customers or potential
customers at their own locations.
TEST ADMINISTRATION
Organizations may use other terms as well,

such as factory acceptance testing and site
acceptance testing for systems that are
tested before and after being moved to a
customer’s site.
TEST ADMINISTRATION
Characteristics of Test Levels

TEST ADMINISTRATION
Characteristics of Test Levels

THANK YOU FOR LISTENING

Lecture5 Part1 IT309

Uploaded by

Copyright:

Available Formats

You might also like

Lecture5 Part1 IT309

Uploaded by

Document Information

Original Title

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

Lecture5 Part1 IT309

Uploaded by

Copyright:

Available Formats

IT-309 SYSTEMS INTEGRATION & ARCHITECTURE 1

Software Development Models

Software Development Models

Software Development Models

V-Model (Sequential Development Model)

Iterative-Incremental Development Model

Iterative LC - Regression Testing

COTS-Oriented Life Cycle

Testing within a Life Cycle Model (V-Model)

For each test levels, the following can be

● Work product(s) being referenced for

● Typical defects and failures to be found

● Test harness requirements and tool support

Typical test objects:

Objectives of Component Testing

Typical test objects:

● System configuration and configuration data

Objectives of Integration Testing

● There may be more than one level of

■ Tests the interactions between

○ System Integration Testing

● Risk analysis reports

Typical test objects:

● System configuration and configuration data

Objectives of System Testing

● The test environment should correspond to

● Effective System Testing needs to be

● Risk analysis reports

Typical test objects:

Objectives of Accepance Testing

or users of a system; other stakeholders

parts of the system or specific non-functional

● Finding defects is not the main focus in

may come after the acceptance test for a

● Acceptance testing may occur at various

○ Acceptance testing of the usability of a

Forms of Acceptance Testing

○ fitness for use of the system by business

● Operational (acceptance) testing

○ Data load and migration task

○ Periodic checks of security vulnerabilities

Forms of Acceptance Testing

○ Contract acceptance testing is

○ Acceptance criteria should be defined

● Alpha and beta (or field) testing

Organizations may use other terms as well,

Characteristics of Test Levels

Characteristics of Test Levels

You might also like