The purpose of this document is to provide a set of application software testing guidelines to ensure that computer systems are properly tested, so as to pursue reliable and quality computer systems.

This document, in essence, suggests a reference model for the planning and carrying out of Application Software Testing. The following serves as an overview of the model:

1. PROJECT ORGANISATION

1.1 Test Control Sub-Committee

A Test Control Sub-Committee is set up to co-ordinate, monitor and resolve priority conflict on the testing activities. The emphasis here is on the necessity of these co-ordination activities. Therefore for those small-sized projects not justifying existence of such sub-committee, its function is still required but is to be achieved through discussion meeting between project team and user representatives.

1.2 Independent Test Group

Where resource constraints are permitted, an independent Test Group within the project team is set up to carry out the testing activities. The emphasis here is on the independent role of the Test Group, which does not necessarily mean dedicated resources.

2. TESTING ACTIVITIES

To test out a computer system from the following 5 different perspectives (the emphasis here is on different perspectives, which do not necessarily mean different testing phases):

1. To validate individual program modules against program specifications (Unit Testing);

2. To validate program linkages against design specifications (Link Testing);

3. To validate integrated software against functional specifications (Function Testing);

4. To validate the integrated software against specifications on operating environment (System Testing); and,

5. To validate the integrated software against end-user needs (Acceptance Testing).

3. TESTING DOCUMENTATION

To document testing activities through the use of Test Plan, Test Specification, Test Incident Report, Test Progress Report and Test Summary Report.

4. TEST PLANNING CONTROL

4.1 Progress Control

To monitor day-to-day progress of the testing activities through the use of Test Progress Reports.

4.2 Quality Control / Assurance

Testing documentation be compiled by Test Group and endorsed by Test Control Sub-committee / Project Committee.