FUNCTIONAL
TESTING TEQNIQUES
Selecting a technique
Functional System Testing Techniques
Requirements testing Regression testing Error-handling testing Manual-support testing Intersystem testing Control testing
REQUIREMENTS TESTING
Must verifies that system can perform
correctly over the continuous period of time.
The system can be tested throughout the
OBJECTIVES
User requirements are implemented.
Correctness is maintained over extended processing periods.
Application processing complies with the organization’s policies and procedures. The system processes accounting
OBJECTIVES
Secondary user needs have been included, such as:
Security officer
Database administrator Internal auditors
Comptroller
Systems process information in accordance with
HOW TO USE
Requirements testing is primarily performed
through the creation of test conditions and functional checklists.
Test conditions are generalized during
the requirements phase, and become
WHEN TO USE
The process should begin in the
REGRESSION TESTING
Regression testing retests previously
tested segments to ensure that they still function properly after a change has
OBJECTIVES
Determining that system documentation
remains current
Determining that system test data and
conditions remain current
Determining that previously tested
HOW TO USE
Regression testing is retesting unchanged segments of the
application system. It normally involves rerunning tests that have been previously executed to ensure that the same results can be achieved
While the process is simple in that the test transactions have
WHEN TO USE
Regression testing should be used when there
is a high risk that new changes may affect unchanged areas of the application system.
In the developmental process, regression
WHEN TO USE
In the maintenance phase, regression
testing should be conducted if the
ERROR- HANDLING TESTING
One of the characteristics that differentiate
automated from manual systems is the pre determined error-handling feature.
Error-handling testing determines the
ability of the application system to
OBJECTIVES
Determining that all reasonably expected error
conditions are recognizable by the application system
Determining that the accountability for processing
errors has been assigned and that the procedures provide a high probability that the error will be
corrected
Determining that reasonable control is maintained
HOW TO USE
Error-handling testing requires a group of
knowledgeable people to anticipate what can go wrong with the application system. Most other forms of testing involve
verifying that the application system
HOW TO USE
Error-handling testing should test the
WHEN TO USE
Error testing should occur throughout
the system development life cycle
At all points in the developmental
MANUAL-SUPPORT TESTING
The manual part of the system requires
OBJECTIVES
Verifying that the manual-support procedures are
documented and complete
Determining that manual-support responsibility has
been assigned
Determining that the manual-support personnel are
adequately trained
Determining that the manual support and the
HOW TO USE
Manual testing involves first the
evaluation of the adequacy of the
process, and second, the execution of the process.
Manual-support testing normally involves
HOW TO USE
Manual-support testing should occur without
the assistance of the systems personnel. The manual-support group should operate using the training and procedures provided to them by the systems personnel. However, the
WHEN TO USE
extensive manual-support testing is best
done during the installation phase so that clerical personnel do not become involved with the new system until
WHEN TO USE
This avoids the confusion of knowing two
systems and not being certain which rules to follow.
During the maintenance and operation phases,
manual-support testing may involve only providing people with instructions on the changes and then verifying that they
INTERSYSTEM TESTING
Intersystem testing is designed to
OBJECTIVES
Determining that the proper parameters and
data are correctly passed between applications
Ensuring that proper coordination and timing of
functions exists between the application systems
Determining that the documentation for the
HOW TO USE
One of the best testing tools for
intersystem testing is the integrated test facility. This permits testing to occur in a production environment and thus the
WHEN TO USE
Intersystem testing should be conducted
whenever there is a change in parameters between application systems.
The extent and type of testing will
WHEN TO USE
If the integrated test facility concept is
used, the intersystem parameters can be verified after the changed or new
CONTROL TESTING
Control testing is designed to ensure
that the mechanisms that oversee the proper functioning of an application
OBJECTIVES
Accurate and complete data
Authorized transactions
Maintenance of an adequate audit trail of
information
Efficient, effective, and economical process
HOW TO USE
The term “system of internal controls” is
frequently used in accounting literature to describe the totality of the mechanisms
that ensure the integrity of processing
Controls are designed to reduce risks;
WHEN TO USE
Control testing should be an integral part
of system testing.
Controls must be viewed as a system
PARALLEL TESTING
Parallel testing is used to determine that
OBJECTIVES
Conducting redundant processing to
ensure that the new application performs correctly
Demonstrating consistency and
HOW TO USE
Parallel testing requires that the same input data be run through two versions of the same application.
Parallel testing can be done with the entire application or with a segment of the application.
WHEN TO USE
Parallel testing should be used when there is
uncertainty regarding the correctness of
processing of the new application, and the old and new versions of the applications are
similar.
parallel testing is one of the more effective
Any Questions !!!
END OF LECTURE
