Design And Implementation Of A Distributed Recruitment Management System

The minimum requirements for the documentation are:
It must be reviewable: That is, the records must be sufficient for others to review the adequacy of the testing.
It must be sufficient for the tests to be repeatable: This is important for regression testing - unless you are sure you can repeat a test, you can never be sure if you have fixed the cause of a test failure. Repeatability is also important for analysing failures both failures during the initial testing, and subsequent failures. Knowing exactly what was and was not tested, and exactly what passed and what failed during testing is an invaluable aid in isolating difficult-to reproduce field failures. Repeatability not only implies the need to record in reasonable detail how the test is run and what data is used, but also implies identification of the version of code under test.
The records must be archivable: That is, they must be sufficiently well kept and identified that they can be found if required, at a later time (perhaps years later when analysing a failure) (Rodney Parkin, 1997).
Software testing is an integral part of an efficient and effective strategy for testing systems. It is best performed by the designer of the code under test. The appropriate level of formality and thoroughness of the testing will vary from project to project, and even within a project depending on the criticality, complexity, and risk associated with the project.
In the course of the development of the recruitment management system unit testing was utilised to ensure the software’s specification defined in previous sections were met.

The dashboard in fig 4.3 shows us the basic operations that can be performed by a company utilising the R.M.S. In summary there are 8 basic operations which can be performed with some of these operations having sub-operations each of these operations were tested below with the appropriate responses generated by the system shown.