Testing

System or 'application' testing should result in a clear picture as to whether all code modules work as specified, and that the system as a whole performs adequately on the platform and across the network on which it will be deployed.

Even if the system being implemented is already running within other organisations under similar conditions, it is crucial to develop a comprehensive plan to thoroughly test it before going live. The testing should examine whether:

• the whole system is properly configured;
• the hardware on which the system is to run is properly installed;
• system parameters are properly set;
• the functionality of the software is sound and performs as expected;
• the business processes are supported;
• any local conditions and requirements are satisfied.

This section assumes to some extent that adequate selection and procurement procedures have been carried out and that the software being implemented is appropriate for the process requirements. However, it is certainly possible to discover loopholes in the testing phase which may lead to further process redesign or even elements of re-scoping, depending on their severity. Indeed, much of the material presented here can be used as a basis for the initial selection (the test scripts in the System Selection infoKit are a form of functionality testing but at that stage are not product-specific).