0% found this document useful (0 votes)
58 views19 pages

System and Functional Testing

Uploaded by

Kyla Euste
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
58 views19 pages

System and Functional Testing

Uploaded by

Kyla Euste
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 19

SYSTEM

AND
FUNCTIONA
L TESTING
KYLA MAE F. EUSTE
BSN 2K
System and functional testing are critical components
of the system life cycle, whether the software or system
is under new development or is commercial off-the-shelf
(COTS) software that is being configured for a customer’s
specific needs.
Testing definitions and goals have evolved, from the most
simplistic “bug detection” process, conducted toward the end
of the design and coding phases. To the more contemporary
definition that goes far beyond bug detection to include
alignment of the technology to the business goals, with the
intent that the software does what it is supposed to do, and
errors are caught and resolved very early in the development
process.
Quality assurance is a proactive, planned effort to ensure that a
defect-free product fulfills the user-defined functional requirements.
This guarantee that a product being marketed is “fit for use”.

Testing is all about finding defects.


Quality assurance is all about
preventing defects.

TESTING
Testing is composed of activities performed at various intervals
during the development process with the overall goal of finding
and fixing errors. The system life cycle phase usually drives how
testing activities are organized, but the testing plan will
normally include coordination of test efforts, test execution,
defect management, and a formulation of a test summary.
Requirements Analysis
1 User needs are compared to the
documented requirements
Ambiguity Reviews
TEST
2 Identification of flaws, omissions, and PLANNING
inconsistencies in requirements and specifications

Nonredundant Test Script Design


3 All key functions are tested only
once in the scripts.
Creation of Test Data
4 The right kinds of test patients and
data to test all functions

Problem Analysis
5 Defect management includes
uncovering underlying issues
Coverage Analysis
6 The scripts will test all key functions, and all key
nonfunctional components and features
STANDARDS
the third element of quality assurance, involves the
creation and enforcement of testing standards,
process improvement activities related to QA,
evaluation and appropriate use of automated testing
tools, and quality measures.

Software quality assurance is a planned effort to


ensure that a software product fulfill verification and
validation testing criteria and additional attributes
specific to the project, for example, portability,
efficiency, reusability, and flexibility.
TESTING MODELS &
METHODOLOGIESPROCESS
REDESIGN
WATERFALL
MODEL LOGICAL DESIGN

characterized by
relatively linear PHYSICAL DESIGN
phases of design,
development, and
testing. UNIT DESIGN

CODING
TESTING MODELS &
METHODOLOGIES
DEFINE
TESTING
This Iterative
software
development model
employed cyclical IMPLEMENT DEVELOP
repeating phases,
with incremental
enhancements to the
software.
The main advantage TEST BUILD
of an iterative
approach was earlier
validation of
prototypes, but the
costs of multiple
TESTING MODELS &
METHODOLOGIES
Characteristics include the
AGILE following:
SOFTWARE
• Generation of business stories
DEVELOPMENT
Characterized by to define the functionality.
nearly • On-site customer or end-user
simultaneous presence for continual feedback
design, build, and and acceptance testing.
testing. • Programmer–tester pairs to
Extreme align coding with testing—and in
Programming (XP) fact, component test scripts are
is a well-known expected to be written and
Agile automated before code is written.
development life • Integration and testing of code
cycle model that are expected to occur several
emphasizes end- times a day.
user engagement. • Simplest solution is
TESTING MODELS &
METHODOLOGIES
AGILE SOFTWARE
SCRUM DEVELOPMENT-
A project SCRUM PROJECT
management
MANAGEMENT
method that
accelerates
MODEL some
Encompasses
communication by all key quality assurance
team members, principles, is
including customers adaptable to
or end users, healthcare
throughout the information
project. A key technology COTS
principle of Scrum is implementation
the recognition that projects, and the
customers are likely intense end-user
to change their participation almost
TESTING TYPES

Acceptance Ad hoc Alpha


End-user validation Off-script testing First customer use
testing or final intended to discover of an application
testing based on issues; “try to break nearing
end-user it” development
requirements completion
TESTING TYPES

Beta Black Box Comparison


Customer use when Cases developed for Assessing against
development is functional testing competitor
complete, to uncover products
any additional issues
before general
release
TESTING TYPES

Compatibility Coverage Database


Software performance Each branch has Integrity of DB field
in different true and false values
environments outcomes; each
(with various software,
hardware, network,
condition considers
operating systems) all possible
outcomes
TESTING TYPES

End-to-end Exception Exploratory


System testing that Error messages and Informal testing,
mimics real-world exceptions— often untrained
environment identification and users, to identify
handling processes unimagined issues
TESTING TYPES

Functional Integration Interoperability


Focused on meeting Testing application Disparate systems
user-defined parts to ensure they are able to
requirements; function together exchange a defined
includes unit / correctly; can mean
component, “pieces of code”
data set, as in
integration, regression, within a module, or Health Information
and acceptance between modules Exchange
testing
TESTING TYPES

Load Nonfunctional Parallel


High volume Testing outside of the Literally “side by
testing, often user requirements that side” testing: Same
automated, to define the functions; work done in old
determine typically includes system and new
point at which interoperability,load/ system to compare
system response volume, performance/ results
time degrades reliability, efficiency,
security
TESTING TYPES

Performance Recovery Regression


Often used Testing recovery Testing planned
interchangeably time after a changes for
with stress—may software crash or unintended ripple
include volume, hardware failure, or effects
reliability other failure
TESTING TYPES

Security Stress System


How well does Similar to load Includes functional
system protect testing: Functional and nonfunctional
against testing for very high testing, using
unauthorized loads of users, both black box and
use, damage, data queries, repeated white box
loss, etc. inputs, etc techniques
TESTING TYPES

Unit Usability White Box


Lowest level that Focus on ease of Testing the logic
focuses on a use as defined by paths based on the
selected function or end users defined specifications
piece of code to see
if it works as
designed—usually
performed by the
programmer or
builder

You might also like