Test Techniques
• REQUIREMENTS TESTING - Assures that the system performs as specified in order to meet the needs of the
users. The specifications map back to specific requirements and those requirements represent the real and
complete user set of requirements. All policies and regulations have been adhered to. Requirements
testing looks for complete traceability of each discrete requirement statement to each detail unit of
technology implementation and documentation.
• REGRESSION TESTING - Assures that anything unchanged still performs correctly. All unchanged system
components still function as expected and all manual procedures surrounding the systems are still correct.
The potential scope of testing is theoretically largest in regression testing since the entire universe of
technology and documentation outside of a project's scope should be retested to assure no negative
unplanned impacts. In fact, risk assessment can be used to dramatically limit the scope of regression
testing to those technology and documentation components that are reasonably at risk.
• ERROR HANDLING TESTING - Assures that errors can be prevented or detected, and then corrected. A variety
of errors of different severity are intentionally introduced into the test cycles.
• MANUAL SUPPORT TESTING - Assures the people-computer combination produces the right result. All manual
procedures required to use and operate the system functions have been developed and implemented.
• INTERSYSTEMS TESTING - Assures that data is correctly passed from system to system. All intersystem
parameters have changed and foreign system documentation has been updated.
• CONTROL TESTING - Assures that controls reduce system risk to an acceptable level. All data and process
reconciliation procedures work with all appropriate manual controls in place.
• PARALLEL TESTING - Old systems and new system are run and the results are compared to detect unplanned
differences. The old and new system outputs can be reconciled within the limits imposed by new system
functions.
• STRESS TESTING - Assures that the system performs with expected high volumes. Sufficient technical
resources have been allocated so that operational capability can be maintained under maximum volume
and pressure.
• EXECUTION TESTING - Assures that the system achieves desired level of performance. All transaction
turnaround time is adequate and execution doesn't preclude other operational activities within the technical
environment.
• RECOVERY TESTING - Assures that the system can be returned to an operational status after a failure.
Backup data and recovery procedures are in place and working, including major disaster recovery planning
and rehearsal.
• OPERATIONS TESTING - Assures that the system can be executed in a normal operational status. Only
production documentation is needed in order to operate system functions.
• COMPLIANCE TESTING - Assures that the system is developed in accordance with standards and procedures.
All standards have been followed and all documentation is complete and in place.
• SECURITY TESTING - Assures that the system is protected in accordance with importance to organization.
