WMS TESTING

**********

**********

The testing phase of a WMS implementation is probably the most important part of the installation process. Not only should this stage be used to ensure that the software provided by the WMS supplier works, but it is also a time to validate process's and procedures and ensure that data setup has been completed correctly.

**********

It is important when selecting a group of people to be utilised as the testing team that the right types of employees are chosen. The ideal personnel should have an overall understanding of the current operational and system working practices. They should also have the ability to work on their own initiative and be able to generate alternative solutions to system and operational issues that will occur during the testing phase of the project.

A common issue with system testing from a customer perspective is that the people engaged to work with the software have no knowledge of the application and have not performed this exercise before.

This is because these people tend to be key operational employees, and are not used to carrying out so much work sat in front of a computer terminal. Therefore it is essential that the testers receive as much training as possible from the software providers prior to testing commencing.

Testing is carried out to ensure that the system works accurately and effectively before it is implemented into a live operation. The first action to be decided upon is the scope of the tests.

These should include all clerical, software, hardware and interface aspects within all areas. Testing should not only be carried out on correct data flows alone, but should also include the transmission of information that is just outside the acceptable ranges. This is to ensure that the system will reject the information and not accept the wrong data undetected.

Before any testing takes place, it is important to identify which particular feature of the system is to be tested i.e. What the objective of the test is. From the objective desired results can be established. The end result of any testing should be the demonstration that what should have happened has happened. All of the results from every individual test should be recorded. A test should only be passed when the actual results match the expected results.

EXDS has undertaken several "testing" projects covering the following activities:

  • Defining and planning the testing program.
  • The writing of detailed test scripts.
  • Management of user acceptance testing.
  • Management and planning of integration testing.
  • Management and planning of volume testing.
  • Management and planning of fail over testing.
  • Management and planning of conversion and backout testing.

**********

Layout, content, design and revisions Copyright 2001, EXDS Limited