8.0 - System Testing
8.0 - System Testing
System Testing
• Question asked: “Is the problem solved ?”
• can be thought of as a progression of
steps, from testing for functional
requirements (function testing) and
non-functional requirements (performance
testing) to see if the developer’s
implementation agrees with the customer’s
written requirements, to acceptance and
installation testing to see if the customer is
happy with the result.
Steps in System Testing
(1) Function Testing – checks that the
integrated system performs its functional
requirements as specified in the
requirements.
(2) Performance Testing – compares the
integrated modules with the
nonfunctional system requirements. These
requirements include security, accuracy,
speed, and reliability; they constrain the
way in which the system functions are
performed.
Steps in System Testing
(3) Acceptance Testing – checks the
system’s characteristics to assure that
they are in compliance with the
defined requirements.
(4) Installation Testing – is done to
allow users to exercise system
functions and document additional
errors.
• The members of the test team can enter
each step of testing knowing what is
needed as input; what procedures should
be followed; what to expect on the
display screen in databases, or as printed
output, and how to report errors or
discrepancies.
• Once testing is complete, the system is
delivered to the customer.